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: <1044893905.11857.12.camel@nh--1614-2.nh.pearsoned.com>
From: kdebisschop at alert.infoplease.com (Karl DeBisschop)
Subject: SQL Slammer - lessons learned

On Mon, 2003-02-10 at 10:23, David LaPorte wrote:
> Not sure if this is dated (I'm not an AT&T customer), but AT&T was filtering 
> port 80 as a result of Code Red.  This document leads me to believe it will 
> continue indefinately.
> 
> http://help.broadband.att.com/faq.jsp?content_id=792&category_id=54
> 
> (you need to choose your state and choose Broadband Internet)

ATT in Quincy and Middleborough, MA, have lifted that restriction. I
have no other data points. (Other than yes, I do get code red and nimda
fingerprints in my server logs)

--
Karl