full-disclosure - [Dshield] Re: Windows Messenger Popup Spamon UDP Port 1026

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]

From: jstewart at lurhq.com (Joe Stewart)
Subject: [Dshield]  Re: Windows Messenger Popup Spamon UDP Port 1026

On Saturday 21 June 2003 05:02 pm, morning_wood wrote:
> the point being there should be no isp blocking of any ports period.
> Why? For what purpose? I would seek another provider if my ISP
> purposefly blocked ports. 

wood, 
Your ISP (AT&T) already blocks inbound TCP ports 137, 138, 139 and 1080.

-Joe

-- 
Joe Stewart, GCIH 
Senior Intrusion Analyst
LURHQ Corporation
http://www.lurhq.com/