similar to: ssh-agent w/timeout: does ssh-add reset that timeout?

OK. I've had a few replies to my earlier question about auth agent forwarding that indicate that it is currently supported. So now I'm confused as to why it is not working for me. I'm trying to chain between servers. With v1 I could load my key into the ssh-agent on my workstation (a) and ssh to server b and ssh from there to server c, all without typing a passphrase/password. Now

http://bugzilla.mindrot.org/show_bug.cgi?id=496 ------- Additional Comments From markus at openbsd.org 2003-02-19 01:15 ------- that's not too hard with the current code, and you could use the 'passwd' lock feature for something similar: specify timeout x and enter passwd on agent startup. after x seconds of activity the agent will 'autolock'. use ssh-add -X to unlock

during my seminar of advanced exploitation techniques (SEAT, [1]) i developed some methods to crack into system via DMA (e.g. via firewire). as part of this i developed a program that steals loaded ssh private keys from ssh-agents. i was astonished to find that the keys are not immediately removed from the agent when a timeout occurs, but only the next time the agent is queried via its socket. i

http://bugzilla.mindrot.org/show_bug.cgi?id=496 Summary: add a timeout function to ssh-agent Product: Portable OpenSSH Version: older versions Platform: All URL: http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-add OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component:

http://bugzilla.mindrot.org/show_bug.cgi?id=496 ------- Additional Comments From hauser at acm.org 2003-03-31 16:56 ------- Created an attachment (id=266) --> (http://bugzilla.mindrot.org/attachment.cgi?id=266&action=view) Readme.txt for the japanese win-ssh-agent.exe/win-ssh-askpass.exe proofread by Nayuta ------- You are receiving this mail because: ------- You are the assignee

And lsof the agent too - see what files it has open... Nico -- > -----Original Message----- > From: Kevin Steves [mailto:kevin at atomicgears.com] > Sent: Friday, August 23, 2002 4:48 PM > To: openssh-unix-dev at mindrot.org > Cc: stevesk at pobox.com > Subject: Re: 3.4p1 ssh-agent auth-retry patch available: was: Re: > Updated ssh-agent authentication retry patch available

After installing this OpenSSH build on our AIX v5.2 systems, some users started complaining that their logins failed. We are using the binary build "OpenSSH 4.3p2-r2 for AIX 5.2" posted on http://sourceforge.net/projects/openssh-aix/ Digging deeper, we find that these failing users have their clients configured to use ssh-agent. this appears in the syslog at the time of their attempted

https://bugzilla.mindrot.org/show_bug.cgi?id=2228 Bug ID: 2228 Summary: ssh-agent passwords do not timeout properly Product: Portable OpenSSH Version: 6.4p1 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh-agent Assignee: unassigned-bugs at

I wrote a patch to make the number of times and and the delay between retries that ssh attempts to talk to ssh-agent configurable. This patch is indispensible when running multiple ssh sessions in parallel from a script (e.g. to run commands on a large number of hosts); without the patch, many ssh sessions simply fail because they cannot contact the agent, rendering the mechanism unusable. If

Hey guys, I installed OpenSSH 7.9p1 on Windows Server 2016 and generated a SSH key pair with ssh-keygen on my Windows 10 Client (OpenSSH 7.6p1). I can connect to the server with "ssh user at domain@servername -i id_rsa". But as soon as I add the private key to the SSH agent by "ssh-add id_rsa" this does not work anymore and aborts with the message "Permission denied

https://bugzilla.mindrot.org/show_bug.cgi?id=2411 Bug ID: 2411 Summary: ssh-agent flag to print details of existing agent Product: Portable OpenSSH Version: 6.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh-agent Assignee:

On 13.01.16 10:27, Richard W.M. Jones wrote: > On Wed, Jan 13, 2016 at 09:55:53AM +0200, Shahar Havivi wrote: > > Hi, > > > > I am successfully importing VM from Xen server at oVirt project via virt-v2v. > > I am setting ssh-agent and running ssh-add before the import process, > > after the import done I am trying to kill the agent via: > > ssh-agent -k (and

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is

http://bugzilla.mindrot.org/show_bug.cgi?id=496 hauser at acm.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|add a timeout function to |add a user-friendly timeout |ssh-agent |function to ssh-agent ------- Additional Comments From hauser

Hi all, i'm trying to figure out if i'm being silly or if there is a genuine problem. Running on the notorious Redhat 7, 2.2.16-22 #1, X86. [user at host]$ ssh-agent -s SSH_AUTH_SOCK=/tmp/ssh-XXYFcFR6/agent.2101; export SSH_AUTH_SOCK; SSH_AGENT_PID=2102; export SSH_AGENT_PID; echo Agent pid 2102; [user at host]$ echo $SSH_AUTH_SOCK [user at host]$ echo $SSH_AGENT_PID [user at host]$

Hello All, I've just attempted to build from -cvs on AIX and get the following: $ gcc [snip] -c ssh-agent.c ssh-agent.c: In function `main': ssh-agent.c:975: `BSDoptarg' undeclared (first use in this function) ssh-agent.c:975: (Each undeclared identifier is reported only once ssh-agent.c:975: for each function it appears in.) make: 1254-004 The error code from the last command is 1.

Hi, I am successfully importing VM from Xen server at oVirt project via virt-v2v. I am setting ssh-agent and running ssh-add before the import process, after the import done I am trying to kill the agent via: ssh-agent -k (and setting the SSH_AGENT_PID environment), but I get the following error: kill: No such process Can you please explain why there is no agent? Do I need to delete the agent?

Hi, I run into a certain problem from time to time. 1. Configure and launch ssh-agent. 2. That's usually perfect. 3. Occasionally, connect to a different and less common remote server. Use ssh -i keyfile 4. ssh -i keyfile fails. Because ssh-agent doesn't know about that key. If you are specifying a key "-i key", then you are specifying a key, and clearly don't need to use

On Fri, Sep 18, 2015 at 7:07 PM, Peter Stuge <peter at stuge.se> wrote: > Fabiano Fid?ncio wrote: >> A few possible solutions for this would involve a way to support more >> than one agent, talking to both (the local one and the spice one), >> merging then their responses and returning it to any application who >> sent the request. Note that would be really nice if

Folks, MacOSX 10.6.x (Snow Leopard) runs { ssh-agent -l }; that's not an s/ssh-add/ssh-agent/ typo. It appears to be an undocumented addition (the man-pages were not updated). I *suspect* that it just tells the agent to honour whatever pre-existing value of $SSH_AUTH_SOCK it inherits and to try to listen to that. I don't know for sure. Does anyone have details on what exactly it does,