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: <43185EE4.2010003@baden-online.de>
Date: Fri Sep  2 15:17:20 2005
From: peer at baden-online.de (Peer Janssen)
Subject: router naming

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