Full Disclosure mailing list archives
Re: [Dshield] Re: Windows Messenger Popup Spamon UDP Port 1026
From: Joe Stewart <jstewart () lurhq com>
Date: Mon, 23 Jun 2003 08:43:21 -0400
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/ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Windows Messenger Popup Spam on UDP Port 1026 Joe Stewart (Jun 20)
- Re: Windows Messenger Popup Spam on UDP Port 1026 morning_wood (Jun 20)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Johannes Ullrich (Jun 21)
- Re: [Dshield] Re: Windows Messenger Popup Spamon UDP Port 1026 morning_wood (Jun 21)
- 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)
- Re: [Dshield] Re: Windows Messenger Popup Spam on UDP Port 1026 Johannes Ullrich (Jun 21)
- Message not available
- Re: Windows Messenger Popup Spam - advisory amended Joe Stewart (Jun 23)
- Re: Windows Messenger Popup Spam on UDP Port 1026 morning_wood (Jun 20)
- 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)