Uploaded gopher 2.3.1-1 (source alpha) to master
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.6
Date: Thu, 17 Aug 2000 15:16:07 -0500
Source: gopher
Binary: gopher gopherd
Architecture: source alpha
Version: 2.3.1-1
Distribution: unstable
Urgency: low
Maintainer: John Goerzen <jgoerzen@complete.org>
Description:
gopher - Distributed Hypertext Client, Gopher protocol
gopherd - Gopher server
Changes:
gopher (2.3.1-1) unstable; urgency=low
.
* Initial re-release. Package had been yanked after 1995 due to licensing.
* UMN has just GPL'd gopher.
* This package contains the security fix from bugtraq.
* I have patched it to chroot() and setuid() earlier for better
security.
SIDE EFFECT: logging will not work if chroot() is used.
* The extension chopping code was buggy, so I have removed it.
* Made many fixes to eliminate compiler warnings and errors.
* Removed redefinitions of sys_errlist
* Included more header files to bring in relevant prototypes
* Modified to use Debian paths
* Modified configure.in to look for -lcrypt
* Modified Makefile.config.in to use -Wall
* Removed -DSETPROCTITLE from configure.in to make start-stop-daemon
work better.
* Added logrotate
* Wrote Debian support from scratch.
* AUTH.h includes crypt.h
* gopherd/Makefile.in uses separate conffile dir (Debian path)
* STRstring.h had a paren problem; gcc on alpha brought it out. Fixed.
* String.h was missing some header files.
* Other fixes.
Files:
07ed7e10088754359cdcdaa68ceddd6d 577 net optional gopher_2.3.1-1.dsc
6bcba4a5690f7977bc3ce7ea82cfef52 464227 net optional gopher_2.3.1.orig.tar.gz
8159fa7265fe680a8bc538cd8ea3e825 26128 net optional gopher_2.3.1-1.diff.gz
b8f8c2fcfea9462fa536bff89d0304b3 150150 net optional gopher_2.3.1-1_alpha.deb
af39019df0cd62e6de7bc1c2462a17e6 130196 net optional gopherd_2.3.1-1_alpha.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5ozQs3PeFtIodmh8RAlx/AJ42Bi+V9grTLUPKhHM4monyRhXauQCdG8Be
vVogKQeX5H1twj6MA/zyYo4=
=+J7X
-----END PGP SIGNATURE-----
Reply to: