full-disclosure - 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]

From: bugtraq at war-driving.org (Marcus Specht)
Subject: Windows Messenger Popup Spam on UDP Port 1026

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 20 Jun 2003 22:37:46 -0400, Joe Stewart wrote:

> Due to widespread abuse, many ISPs have moved to block
>inbound traffic on UDP port 135. It appears the spammers have adapted,
>so ISPs are urged to block UDP port 1026 inbound as well.

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.

If the customer is too stupid to even use a (personal) firewall then it might be better not to use the internet.

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0

iQA/AwUBPvS66yL+kvidU8B4EQJzGwCg8bnD//fTqdJyv76jOPn8eDCtdFcAn0dd
UuM6Jj6udAN4VnS95vSUgahS
=Rnd6
-----END PGP SIGNATURE-----