[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted bastille 1:2.0.1-1 (i386 source)



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.7
Date: Mon, 19 Aug 2002 13:21:12 +0200
Source: bastille
Binary: bastille
Architecture: source i386
Version: 1:2.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <jfs@computer.org>
Changed-By: Javier Fernandez-Sanguino Pen~a <jfs@computer.org>
Description: 
 bastille   - Security hardening tool
Changes: 
 bastille (1:2.0.1-1) unstable; urgency=low
 .
   * New upstream release.
   * Now provides a postrm to remove all logs and configuration files placed
     by Bastille (could be useful if a user installs Bastille, uses it and
     then removes it from the system. Note: in this case the firewall would
     not work, of course)
   * Removed psad (there's a New Maintainer packaging it, it will be integrated
      into Bastille as soon as the package is done). Bastille now Recommends:
      psad (should it recommended firewalling code too???)
   * IMPROVED:
         Added a new debugging option (-d) for those #print statements in API.pm
   (should be used by developers to populate other modules)
         Changed bastille to provide the -v, -d and -l options to the Backends
         Also changed InteractiveBastille to reflect what API.pm says
         Questions.txt now includes some information specific to Debian
         (chkconfig stuff mostly)
         Added a bastille-makejail.py example for 'makejail' to build a
         chrooted testing environment (works for me, YMMV)
   * FIXED:
  	InteractiveBastille did not show Usage because GLOBAL_ERROR was not
   	exported in API.pm *and* because API.pm was not loaded before
  	showUsage was called
  	RootTTYLogins fixed to remove *all* ttys, not just tty1-tty6,
  	tty10-tty60....
  	Bastille manpage now properly displays valid options
  	Some links (called chkconfig) are provided for Debian (need to provide
  	more by checking which runlevel/number is used by some packages)
   * CHANGED:
   	The init script will not launch if no bastille-firewall.cfg exist
    	There is no /var/lock/subsys, /var/lock/bastille used instead
   * TODO: Port the fixes done to previous versions.
Files: 
 525fe907ff63217dc385ffeac914042f 685 admin optional bastille_2.0.1-1.dsc
 ea9786fa0f41026be6dc8ebc302c76f4 251592 admin optional bastille_2.0.1.orig.tar.gz
 590a3c8da8336b23d0e26c2c372b7070 7610 admin optional bastille_2.0.1-1.diff.gz
 0aab1076024a5d402dcc0fa126564ba9 291036 admin optional bastille_2.0.1-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBPaLwOftEPvakNq0lAQGSPAP/Xz5r4IJRqi0ToGdzzjb8XSMP8sI8yO+Y
ipW9jb7xUzMTSQomzuQqZOuNJ8MBs9ux0eX1h7TkZQUga4efRUzf3nksGVypgyjn
XG81XQHewh4+F0+GAwI4iBDF+xEFKgYYgLUrjgEf2JgCO45i30bYpox0r8HaBt0E
ratW3JWmtIw=
=R8Me
-----END PGP SIGNATURE-----


Accepted:
bastille_2.0.1-1.diff.gz
  to pool/main/b/bastille/bastille_2.0.1-1.diff.gz
bastille_2.0.1-1.dsc
  to pool/main/b/bastille/bastille_2.0.1-1.dsc
bastille_2.0.1-1_i386.deb
  to pool/main/b/bastille/bastille_2.0.1-1_i386.deb
bastille_2.0.1.orig.tar.gz
  to pool/main/b/bastille/bastille_2.0.1.orig.tar.gz



Reply to: