full-disclosure - 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]

Message-ID: <acdc033d050902081320c7d347@mail.gmail.com>
Date: Fri Sep  2 16:13:40 2005
From: michealespinola at gmail.com (Micheal Espinola Jr)
Subject: router naming

Actually, GPS coords have a place in DNS records.

On 9/2/05, Peer Janssen <peer@...en-online.de> wrote:
> luca developer wrote:
> 
> > Hi folks
> > Is there a best practice for assign a router name ? e.g.: router type
> > + city + room.id <http://room.id>  and so on
> > Wich method is usually used to assign a router name ?
> 
> 
> "Full-disclosure router naming" would be GPS coordinates, wouldn't it?
> 
> This might proove to be a security risk, though, depending on your
> organization.
> 
> Might be pratical to locate missing (read: walled-in or so) routers --
> if they won't be moved around keeping their then-old name.
> 
> Cheers
> Peer
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
> 


-- 
ME2  <http://www.santeriasys.net/>