-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My intention wasn't to say a default firewall can never work, but
that it
can't work for debian, given the community/ideology and existing
user-base
surrounding it.
Ah, now we disagree: I just think you should have install profiles
and make r
default.
$.000002
_a
- --
alex black, founder
the turing studio, inc.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFGydOsAHZuLuydb2YRAuAsAJ4gdXkilHb7NNUBnC5uKpYoG6VIJACdFZTK
Azi/tVYEPnuIAwLX/atPaE8=
=DJ5Y
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMA
Not that safe, some of those scanners to a portscan first looking for SSH.
I use the old tried-and-true "know who you want accessing the machine" and add
those people/ips to hosts.allow, and deny everything else. Works like a charm,
and just keep a public backdoor machine you can use to hop into
f
you screwed up you only have to wait a few min before
it goes away. If it worked, you just kill the queued
at command line.
top tip!!!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
--
alex black, founder
the t
turns out that the upgrade just clobbered /etc/ssl and replaced (!)
everything in it with the defaults... so I restored everything and it's
working properly now.
weird that it clobbered it, but eh... problem solved.
_a
--
alex black, founder
the turing studio, inc.
510.666.0074
[EMAIL
libssl, no dice.
Anyone else having problems with build versions of libsasl2? Assuming
anyone else is running them? Anyone else have problems with any other
packages and thew libssl update?
danke,
_alex
--
alex black, founder
the turing studio, inc.
510.666.0074
[EMAIL
As always, please cc: my address directly.
thanks,
_alex
--
alex black, founder
the turing studio, inc.
510.666.0074
[EMAIL PROTECTED]
http://www.turingstudio.com
2600 10th street, suite 635
berkeley, ca 94710
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&quo
uot;real" attack I would act as such.
I think i've sealed the config so tight that it is not vulnerable to
any known/public exploits, and besides all the happy scanning tools and
all that, I'd like to have the opinion or someone with excellent
knowledge of debian security.
*** Ple
a report on findings, with a limited overview of techniques and tools
used.
Please send any questions & proposals to me off-list:
[EMAIL PROTECTED]
Please include "whitehat:" in the subject :)
thanks,
_alex
--
alex black, founder
the turing studio, inc.
510.666.0074
[EMAIL PR
9 matches
Mail list logo