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: How necessary is SSH_AUTH_SOCK?

Subject: Re: How necessary is SSH_AUTH_SOCK?
Date: Tue, 03 Oct 2006 00:02:51 +0300
Steven Elliott wrote:

On Fri, 2006-09-29 at 11:11 +0200, Markus Friedl wrote:

On Thu, Sep 28, 2006 at 12:17:17AM -0500, Steven Elliott wrote:

So my question is - Why doesn't ssh-agent default the location of the
socket file to some well known fixed secure location such
$HOME/.ssh/agent?

$HOME might be on a nfs server, so -a $HOME/.ssh/agent is not the default.


How is having the socket file on an NFS server a problem?  I know that
other applications do it, such as evolution / spamd:
    /home/sle/.evolution/cache/tmp/spamd-socket-path-bz4CuE

I'm not sure that evolution do the right things. Maybe ~/.evolution/cache point to directory under $TMPDIR where we can expect write access. As example KDE directory ~/.kde/socket-localhost point to /tmp/ksocket-$USER/ and this is fine.


> [SNIP]

Roumen

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