full-disclosure - AW: Windows Messenger Popup Spam on UDP Port 10 26

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-next>] [day] [month] [year] [list]

Message-ID: <5.2.0.9.0.20030623120034.01cb02a8@194.151.203.161>
From: nils.ketelsen at kuehne-nagel.com (Nils Ketelsen)
Subject: AW: Windows Messenger Popup Spam on UDP
  Port 10 26

At 11:16 23.06.2003 +0200, vogt@...senet.com wrote:

> > A professional ISP does not block any port. Blocking ports
> > can only be done on the customer side. The ISP does not know
> > which port i might need.
>
>This isn't about you. The ISP also has a responsibility to protect
>the internet at large. If millions of spam are sent each day because
>the average user is too stupid to close off his proxy, then the
>ISP can either shut him down, or block the proxy port. Obviously,
>shutting down isn't an option for business reasons.

In this case I would request all ISPs to block port 25. Millions of spams 
are sent via this port each day.

Nils