full-disclosure - Full-Disclosure Posts

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: <Pine.LNX.4.21.0410161931250.18086-100000@kcisp2>
From: mikehome at kcisp.net (Mike Barushok)
Subject: Full-Disclosure Posts

I wonder how they handled the Cisco guy whose actual
legal name was 'megazone' (Without the quotes, IIRC).

Or the chinese couple that wanted to name their kid '@'?
(The symbol ususally pronounced as 'at').


On Sat, 16 Oct 2004, yahoo@...alhost wrote:

> Should Full-Disclosure only allow so-called -real- names? I was on
> Nanog (a network admin list) and they have a rule where you can only
> post with a first and second name, instead of an alias or nick, to
> kind of give more credibility that you are a security professional and
> not a hax0r or script kiddie.
> 
> Should the same rule be pro actively implemented to Full-Disclosure or
> is it a dead duck idea?
> 
> I know hax0rs or script kiddies would probably use fake first and
> second names if it was implemented, but at least the list would look
> neat and a tad more professional?
> 
> Feedback welcomed....
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>