bastille deb (testing) hosed?
This brave lad decided to connect his fairly up-to-date Debian "testing"
branch machine to his cable modem tonight, and then took bastille 1.3.0-2 out
for a test spin. The first complaint was that "Bastille/PSAD.pm" could not be
found:
"Executing PSAD Specific Configuration
"Can't locate Bastille/PSAD.pm in @INC (@INC contains: /usr/lib
/usr/local/lib/perl/5.6.1 /usr/local/share/perl/5.6.1 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.6.1 /usr/share/perl/5.6.1
/usr/local/lib/site_perl . /usr/lib/perl5/site_perl/ /usr/lib/Bastille) at
/usr/sbin/BastilleBackEnd line 78."
A brutish attempt at fixing this:
cp /usr/share/perl5/psad.pm /usr/lib/Bastille/PSAD.pm
brought movement, but only to new loggerheads:
"Executing Logging Specific Configuration
"syntax error at /usr/lib/Bastille/Logging.pm line 122, near ") {"
"syntax error at /usr/lib/Bastille/Logging.pm line 138, near "}"
"Compilation failed in require at /usr/sbin/BastilleBackEnd line 143."
What's odd in the first glitch is that 'dpkg -L bastille' shows in part:
/usr/share/Bastille/Psad.pm
...but this is an _empty directory_!
A search of recent debian-user and debian-firewall brought now mention of
bastille, albeit a lot of discussion of iptable scripts. What's the deal with
bastille?
--
Bob Bernstein
at http://www.ruptured-duck.com
Esmond, Rhode Island
USA
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: