full-disclosure - SQL Slammer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <02d201c2ced2$3f1e4e80$c71121c2@sharpuk.co.uk>
From: DaveHowe at cmn.sharp-uk.co.uk (David Howe)
Subject: SQL Slammer - lessons learned

at Friday, February 07, 2003 2:38 PM, Niels Bakker
<niels=netsys@...ker.net> was seen to say:
> I'm not sure why this issue keeps getting rehashed.  It's been well
> established that a policy of denying all that isn't needed is prudent.
> Also, it's been established that it's not up to connectivity providers
> to force their ideas of proper filters on everyone.
For that matter - we all grew up long enough ago to be able to lock our
own front doors - not rely on someone else to pre-emptively brick
sections up on the offchance that we left that door open accidentally.
One thing I *would* like to see more is ISP willingness to let us
control the filter at *their* side of the pipe; by the time it has
bounced off my firewall it has already used up bandwidth I pay for.