Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: graceful ssh key management

from [Kevin Hunter] Network Security [Permanent Link]
Subject: Re: graceful ssh key management
Date: Thu, 17 May 2007 19:52:55 -0400 
At 5:57p -0400 on 17 MAy 2007, Andrew Raphael wrote:

On Thu, May 17, 2007 at 01:14:44AM -0400, Kevin Hunter wrote:

This means that the client must have four separate private keys, one
each for each server.


Says who? Just use one private/public key pair for all 4 servers.


So, it's a simplified example and certainly a single key set will work,
but in the actual enactment, there are reasons that I need multiple
keys.  The answer that I was looking for is to setup separate keys for
each host in the ssh_config.

Thanks though,

Kevin
[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: graceful ssh key management, Kevin Hunter
Next by Date:  setreuid failed (was: SSH daemon doesn't accept incoming connections), Kirill Kuvaldin
Previous by Thread:  Re: graceful ssh key management, Kevin Hunter
Next by Thread:  logging, Oliver Block
Indexes:  [Date] [Thread] [Top] [All Lists]