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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3E42D94B.6060904@thievco.com>
From: BlueBoar at thievco.com (Blue Boar)
Subject: SQL Slammer - lessons learned

Ron DuFresne wrote:
>>port 1434 on a client (so blocking replies)
> of course the client will reissue the request on aonther port and  get the
> info required.  No harm done.

Maybe for a completely different lookup call, it will.  Meanwhile, the 
blocked lookup comes back as no response, which will be interepreted as no 
such name.

					BB