Mon Dec 25 20:19:05 GMT 2000 Greetings. I noticed that in OpenSSH_2.2.0, DSA keys were allowed to be added to ssh-agent, however the ability for allowing ForwardAgent does not yet seem in place for protocol-2. I've noticed that when using protocol-2, no socket is created in /tmp/ssh-*/, and consequently SSH_AUTH_SOCK is not being set. Hence the ability to ssh to another machine (using protocol-1 or protocol-2) without being asked for a password is lost. Is this something currently under development, or is it just a completely bad idea? If the latter, what are the technical reasons? Cheers. -- primus
openssh-2.2 allows you to use the agent from the host where the agent is running. openssh-2.3 does support agent forwarding, too. -markus On Mon, Dec 25, 2000 at 08:31:36PM +0000, primus wrote:> Mon Dec 25 20:19:05 GMT 2000 > > Greetings. > > I noticed that in OpenSSH_2.2.0, DSA keys were > allowed to be added to ssh-agent, however the > ability for allowing ForwardAgent does not yet > seem in place for protocol-2. > > I've noticed that when using protocol-2, no socket > is created in /tmp/ssh-*/, and consequently > SSH_AUTH_SOCK is not being set. Hence the ability > to ssh to another machine (using protocol-1 or > protocol-2) without being asked for a password is > lost. > > Is this something currently under development, or > is it just a completely bad idea? If the latter, > what are the technical reasons? > > > Cheers. > > -- > primus
Reasonably Related Threads
- ssh-agent, protocol 2, openssh-2.3.0p1
- ssh-agent and ssh-add with openssh-2.2.0p1 on Redhat 7
- Is it good for agent forwarding to creates socket in /tmp/
- 2.5.1p1 ssh-agent path problem in Solaris
- [Bug 1937] New: Make it possible to give a give an ssh session only access to a limit subset of ssh-agent keys