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]

Re: Null-passphrase vs ssh-agent

Subject: Re: Null-passphrase vs ssh-agent
Date: Mon, 13 Mar 2006 19:43:45 -0600
On Mon, 13 Mar 2006 17:06:08 -0500
"Gian G. Spicuzza" <gianspi@gsent.org> wrote:
Thank you for your response. The client must meet the following 
conditions to successfully login:

1) Proper IP
2) Proper Private Key (null-passphrase so at night, when backups are 
initiated, a user does not need to be at console)
3) Appropiate command (scp or rsync)

Since this is a backup-type system, that probably works. Not
*as* secure as a passworded key, but in unattended systems that isn't
always practical. If they key's 0600 the backup user, and the machine
is secure, you should be OK in my (non-expert) opinion. If one machine
is secure, and the other not, set it up so that the secure machine
initiates the connection.  If untrusted individuals have physical
access to the machine with the key, well, you've got problems.

- Michael

-- 
mouse, n: a device for pointing at the xterm in which you want to type.
                -- Fortune

<Prev in Thread] Current Thread [Next in Thread>