full-disclosure - Re: router naming

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]

Date: Fri Sep  2 16:47:20 2005
From: luka.research at gmail.com (luka.research)
Subject: Re: router naming

>How about using FIPS-55.
> Thanks

In my modest opinion I think that with approach like FIPS-55 you can spread 
precious information .to attackers.

e.g: "wich is the major link that connect two city ? ...ok let to see the 
router name... mhhh interesting..."

what about hash key as router name ? e.g.: <hashkey>.corporatedomain

luka.research
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050902/ae4e0497/attachment.html