Full Disclosure mailing list archives
Re: Windows Messenger Popup Spam on UDP Port 1026
From: "Marcus Specht" <bugtraq () war-driving org>
Date: Sat, 21 Jun 2003 22:07:08 +0200
-----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----- _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Re: [Dshield] Re: Windows Messenger Popup Spamon UDP Port 1026, (continued)
- Re: [Dshield] Re: Windows Messenger Popup Spamon UDP Port 1026 Joe Stewart (Jun 23)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Dietmar Goldbeck (Jun 21)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 petard (Jun 21)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Roy S. Rapoport (Jun 22)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Rick Updegrove (Jun 23)
- Message not available
- Re: Windows Messenger Popup Spam - advisory amended Joe Stewart (Jun 23)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Rick Updegrove (Jun 23)
- Re: RE: Windows Messenger Popup Spam on UDP Port 1026 Shawn McMahon (Jun 23)
- Re: RE: Windows Messenger Popup Spam on UDP Port 1026 Niels Bakker (Jun 23)