full-disclosure - [Dshield] Re: Windows Messenger Popup Spam on 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]

Message-ID: <3EF758BC.5000505@updegrove.net>
From: security at updegrove.net (Rick Updegrove)
Subject: [Dshield]  Re: Windows Messenger Popup Spam
 on UDP Port 1026

Johannes Ullrich wrote:

 >Well, blocking port 1026 is probably not such a great idea. But
 >why would a non-windows user suffer if port 135-139 & 445 is blocked?

For example smoothwall firewalls (Linux) require https on 445 but that 
is not the point.  The point is I don't want my ISP to start blocking 
ANY ports for any reason.