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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <003201c5afcd$f54b33b0$4501a8c0@badass>
Date: Fri Sep  2 15:51:49 2005
From: vb at bitsmart.com (vb)
Subject: router naming

personally, i use serial killers...Dahmer=Milwauke, Gacy=Chicago, 
Berkowitz=NY, Bundy=Miami, Ramire=LA, etc. Cant wait to open a Kansas City 
office..
vb
----- Original Message ----- 
From: "Peer Janssen" <peer@...en-online.de>
To: <full-disclosure@...ts.grok.org.uk>
Sent: Friday, September 02, 2005 10:17 AM
Subject: Re: [Full-disclosure] 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
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/ 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ