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: <1044488441.15689.58.camel@utd49554.utdallas.edu>
From: pauls at utdallas.edu (Paul Schmehl)
Subject: SQL Slammer - lessons learned

On Wed, 2003-02-05 at 13:45, Cushing, David wrote:
> 
> Perhaps everyone should start indicating whether they are talking
> about source or destination ports.
> 
> Paul was talking about the destination port that the server was 
> listening on, which will always be 53 for a DNS server.  The only 
> DNS server that will accept a packet on UDP 1434 is a customized 
> one.
> 
Indeed.  Mea culpa for not being specific enough in my statements.
> 
> For all you simpletons who don't know how the internet works, 
> Niels forgot to send you a link :)
> 
> http://www.ietf.org/rfc/rfc1035.txt
> 4.2 - Transport
>
Thanks, David.  I was beginning to think I was going to have to remain
in the dark. :-)

-- 
Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
http://www.utdallas.edu/~pauls/
AVIEN Founding Member