NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
An alternative (Score:1)
http://www.versiontracker.com/moreinfo.fcgi?id=16051&db=mac
This is from the readme file:
-------------------------------------
The Global Agent
The key to making the agent accessible is the SSH_AUTH_SOCK environment variable. The tools in the SSH suite communicate with the agent over a socket whose location is given in the environment variable. If some tool can't read the environment variable, it can't find the socket which means it can't use the agent.
The best way to set an enviroment variable globally is documented in Apple's Technical Q & A 1067. Unfortunately, ssh-agent uses a different socket each time it is launched. So it seems we can't use this method.
The trick is this: we specify a unique file location in the global environment (using the Environment tab in SSH Agent's Preferences pane) and then link that file to the socket ssh-agent uses.
There are a number of rules to follow when using this trick. The most important one is that both ends of a link should reside on the same filesystem. Since ssh-agent creates its sockets in
Reply to This
Re:An alternative (Score:2)
I'm glad to see this, as I've really missed SSHAgentServices. But neither of these solutions is as optimal as SSHAgentServices was, IMO. The ">console" login stuff is a PITA, and I hate the idea that I have to have the SSH Agent application running whenever I want to use SSH (which is to say, all day long!).
I wrote to Kevin Van Vechten, the creator of SSHAgentServices, to see if he'd be willing to update it for Jaguar, but I've not heard back from him. I tried to write him once before, several months a