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: <20030205184834.GA84186@trance.org>
From: niels=netsys at bakker.net (Niels Bakker)
Subject: SQL Slammer - lessons learned

I wrote:

> So, given (1434 - 1023 - 1) other applications that use UDP active, or
> that many outstanding queries, BIND may very well end up using UDP port
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 1434 for a query packet.

Which turns out to be incorrect - BIND allocates one socket only for
outgoing queries, but no entry in /etc/services will keep an operating
system from allocating a port randomly.

	-- Niels.

--