Machine Specific System Name

Rick Stevens rstevens at vitalstream.com
Wed May 4 18:13:21 UTC 2005


Algis Zyle - ISS wrote:
> All,
>  
> I'm sure this is pretty straightforward to someone out there. We've got 
> an application that we'll be re-deploying on numerous hardware platforms 
> (99% are RedHat systems). For Security reasons, what would be a pretty 
> solid way at the OS Level to assign a unique system Id for that specific 
> Hardware/OS Level, etc...Basically a type of Key to prevent unauthorized 
> porting to a different machine. It doesn't have to be 100% failsafe, 
> ease of use is preferred. Uname doesn't seem to give enough information 
> at the Linux Level...Any simple scripts or comments well appreciated.

Hmmmm.  You could use the public RSA or DSA key from ssh-keygen.  The
keys are generated the first time sshd is started.  You'll find the DSA
key in the /etc/ssh/ssh_host_dsa_key.pub file.  The RSA key is in
/etc/ssh/ssh_host_rsa_key.pub.  If you need to generate them WITHOUT
starting sshd, use:

	ssh-keygen -q -t rsa -f /etc/ssh/ssh_host_rsa_key
	ssh-keygen -q -t dsa -f /etc/ssh/ssh_host_dsa_key

They're reasonably secure.  After all, that's how sshd does non-password
authentication.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-      A day for firm decisions!!!   Well, then again, maybe not!    -
----------------------------------------------------------------------




More information about the Redhat-install-list mailing list