similar to: [Bug 496] add a timeout function to ssh-agent

http://bugzilla.mindrot.org/show_bug.cgi?id=500 ------- Additional Comments From djm at mindrot.org 2003-02-24 12:43 ------- I think that: [ -z "$SSH_AUTH_SOCK" ] && eval `ssh-agent -s` [ -z "$SSH_AGENT_PID" ] || ssh-add -l >/dev/null 2>&1 || ssh-add Is as effective and a lot more concise. On the other hand, fragile heuristics like: > export

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=480 ------- Additional Comments From markus at openbsd.org 2003-02-02 00:11 ------- this does not belong to the -L or -l option ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=525 Summary: ad a "cygwin-port" product or component to this bugzilla Product: Portable OpenSSH Version: older versions Platform: All URL: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=831 09 OS/Version: All Status: NEW Severity:

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=479 ------- Additional Comments From hauser at acm.org 2003-01-31 02:59 ------- Created an attachment (id=213) --> (http://bugzilla.mindrot.org/attachment.cgi?id=213&action=view) scvs - a perl script Server-side installation steps as per steiner at acm.org: (1) create one (UNIX) login account with zzh as its login shell. (2) install the

http://bugzilla.mindrot.org/show_bug.cgi?id=481 ------- Additional Comments From markus at openbsd.org 2003-02-02 00:11 ------- do you have a patch for the manpage? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=506 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From djm at mindrot.org 2003-03-10 11:24

http://bugzilla.mindrot.org/show_bug.cgi?id=498 ------- Additional Comments From vinschen at redhat.com 2003-02-19 18:49 ------- Apparently you didn't read /usr/doc/Cygwin/openssh-3.5p1.README. Run ssh-host-config to create the host configuration files and keys and run ssh-user-config to create your personal keys in ~/.ssh. ------- You are receiving this mail because: ------- You are

http://bugzilla.mindrot.org/show_bug.cgi?id=500 ------- Additional Comments From hauser at acm.org 2003-03-31 17:00 ------- BTW, http://bugzilla.mindrot.org/attachment.cgi?id=266&action=edit describes another option how to start it by default under windows. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=500 Summary: show how to start-up ssh-agent by default... Product: Portable OpenSSH Version: 3.5p1 Platform: All URL: http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-agent OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component:

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]$

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

I'm having a path problem with OpenSSH 2.5.1p1 in Solaris (7). When ssh-agent is run, environment variables aren't being passed to the spawned shell. sol# env | wc -l 23 sol# env | grep -i ssh SSH_CLIENT=10.0.1.146 1047 22 SSH_TTY=/dev/pts/0 sol# sol# ssh-agent sh sol# env | wc -l 1 sol# env SSH_AGENT_PID=12032 sol# If I

On Fri, Sep 18, 2015 at 10:58 PM, ?ngel Gonz?lez <keisial at gmail.com> wrote: > On 18/09/15 15:47, Fabiano Fid?ncio wrote: >> >> Howdy! >> >> I've been working on a prototype that allows to do ssh-agent forward >> between a guest, using SPICE, and a spice client >> (remote-viewer/virt-viewer/spicy) >> The whole idea is to have something

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,

Hi all, Thanks for all your hard work! I was particularly excited to see FIDO/U2F support in the latest release. I'd like to make the following bug report in ssh-agent's PKCS#11 support: Steps to reproduce: 1. Configure a smart card (e.g. Yubikey in PIV mode) as an SSH key. 2. Add that key to ssh-agent. 3. Remove that key from ssh-agent. 4. Add that key to ssh-agent. Expected results:

Howdy! I've been working on a prototype that allows to do ssh-agent forward between a guest, using SPICE, and a spice client (remote-viewer/virt-viewer/spicy) The whole idea is to have something similar to "ssh -A guest", but integrated with the desktop environment. As a proof of concept I wrote a standalone ssh-agent that _unlink_ the current running agent in the guest machine and

Hi, I know this might be the most asked question, so I've done anything possible to troubleshoot the problem myself, but still, my SSH Agent Forwarding is not working for me. The best troubleshooting guide that I found, and also the one I've been using, is the ssh forwarding guide on github - https://help.github.com/articles/using-ssh-agent-forwarding I've checked all things there,