full-disclosure - Question

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: <1129941865.90566.12.camel@server1>
Date: Sat Oct 22 01:44:36 2005
From: frank at knobbe.us (Frank Knobbe)
Subject: Question

On Fri, 2005-10-21 at 18:36 -0200, Rodrigo Barbosa wrote:
> The IRC protocol is very easy to identify.
> I would suggest blocking the protocol itself, regardless of the port.

Right. Unless it runs over SSL, then it's a bit harder to identify,
wouldn't you agree?

Cheers,
Frank

PS: Yes, there are bots that are running IRC over SSL, so no "No one
does it" comments please.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20051021/7116b660/attachment.bin