Uploaded caudium 1.0.37-1 (sparc) to ftp-master
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 26 Nov 2001 11:30:23 +0100
Source: caudium
Binary: caudium-dev caudium-modules caudium-ultralog caudium caudium-pixsl
Architecture: sparc
Version: 2:1.0.37-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/sparc Build Daemon <buildd@sparc.debian.org>
Changed-By: Marek Habersack <grendel@debian.org>
Description:
caudium - An extensible WWW server written in Pike
caudium-dev - Development files for Caudium
caudium-modules - C modules for Caudium
caudium-pixsl - Pike XSLT module for Caudium
caudium-ultralog - Log Parser module for Caudium
Closes: 120628
Changes:
caudium (2:1.0.37-1) unstable; urgency=medium
.
* Latest CVS snapshot.
- Added support for //!NOMODULE in modules. This closes the SF bug 473716.
- oldcgi is not not shown in the module list.
- ldapuserauth.pike: fixed a security problem when using user access mode :
it was possible to login as any user by typing any password when user
passwd was not in cache (eg where you were the first to login after a
restart/start of caudium).
- ldapuserauth.pike: crypt problem fixed.
- little fixes with installation on OpenBSD
.
* The init script now checks whether the PID to be killed exists (closes: #120628)
* Updated the standards version
* Got rid of rpath
Files:
ccb40ab05bbef7d13a224fda71843cab 2042084 web optional caudium_1.0.37-1_sparc.deb
558aa3a726a5419c38b7c1017b6bde8e 20456 web optional caudium-modules_1.0.37-1_sparc.deb
b23df5ccba0861ed73ee3b62f5bd4593 23636 web optional caudium-pixsl_1.0.37-1_sparc.deb
fc1b43145b5f2d01c4dfae1cee79459e 64064 web optional caudium-ultralog_1.0.37-1_sparc.deb
687f77fdadeb9b611a85f213374108b1 12006 web optional caudium-dev_1.0.37-1_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAjwC6C0ACgkQgD/uEicUG7A5UACgskcjjM4ITXSLJ0yNoKquOZgv
j0UAn1aN1L7cULc0uXHj60/4El94/2ot
=h73N
-----END PGP SIGNATURE-----
Reply to: