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: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0BKn9uKnWEeCDU7Vx+IAQ8KAAAAQAAAAS6UwgxTmI0aWGFKwzz03TgEAAAAA@online.gateway.strangled.net>
Date: Sat Sep  3 03:46:40 2005
From: aditya.deshmukh at online.gateway.strangled.net (Aditya Deshmukh)
Subject: router naming

> Is there a best practice for assign a router name ?
> e.g.: router type + city + room.id  and > so on
> Wich method is usually used to assign a router name ?

Think of social engg. Put in some name that would not
thing that is not so simple to guess because if someone
manages to figure out how they are assigned then it
might be "game over" from the start

But a properly secured router would not make a huge
difference



________________________________________________________________________
Delivered using the Free Personal Edition of Mailtraq (www.mailtraq.com)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ