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: <20030621194118.GA25651@tin-lizzy.bi.devcon.net>
From: dietmar.goldbeck at acm.org (Dietmar Goldbeck)
Subject: [Dshield]  Re: Windows Messenger Popup Spam on UDP Port 1026

On Sat, Jun 21, 2003 at 01:14:25PM -0400, 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?
> 

I really don't want my ISP to disallow the use of Samba across
Internet connections. If i have to serve documents to windows users,
why not?

(of course i would prefer samba over a vpn, or some other encrypted
file transfer protocol like sftp or webDAV/https).

If ISPs start blocking ports, i would vote for tcp/25.
People should not be allowed to run smtp servers, unless
they have proven knowledge in the relevant RFCs. :-))

  Ciao
   Dietmar

-- 
 Alles Gute / best wishes  
     Dietmar Goldbeck         E-Mail: dietmar.goldbeck@....org
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.