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

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=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

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=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:

http://bugzilla.mindrot.org/show_bug.cgi?id=498 hauser at acm.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Summary|ssh default identity broken?|make ssh default identity |

https://bugzilla.mindrot.org/show_bug.cgi?id=1699 Summary: [patch] Enhance SSH to automatically add keys to ssh-agent Product: Portable OpenSSH Version: 5.3p1 Platform: amd64 URL: http://article.gmane.org/gmane.network.openssh.devel/1 6422 OS/Version: OpenBSD Status: NEW

http://bugzilla.mindrot.org/show_bug.cgi?id=506 Summary: have ssh-agent and ssh-add also support gnupg Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh-agent AssignedTo: openssh-unix-dev at mindrot.org

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=498 Summary: ssh default identity broken? Product: Portable OpenSSH Version: 3.5p1 Platform: All URL: http://www.openbsd.org/cgi-bin/man.cgi?query=ssh OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

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=480 Summary: extend the -l or -L option to mention the ssh-agent's pid 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

It appears there is an opportunity for a denial-of-service attack against ssh-agent when using ForwardAgent. This note describes the circumstances, and provides a patch. Background (not the vulnerability): If ssh-agent is forwarded to a compromised account, a remote attacker could use the connection to authenticate as the owner of the agent. "ssh-add -c" currently defends

My keys are secured with a passphrase. That's good for security, but having to type the passphrase either at every login or at every invocation of ssh(1) is annoying. I know I could invoke ssh-add(1) just before invoking ssh(1), if I keep track of whether I invoked it already, or write some hacky scripts; but the rest of OpenSSH is wonderfully usable without any hacks. Hence, this patch.

https://bugzilla.mindrot.org/show_bug.cgi?id=2739 Bug ID: 2739 Summary: ssh-add no longer works with xargs Product: Portable OpenSSH Version: 7.4p1 Hardware: amd64 OS: Mac OS X Status: NEW Severity: minor Priority: P5 Component: ssh-add Assignee: unassigned-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=479 Summary: add description how to run a ssh tunnel without a full shell on the remote site Product: Portable OpenSSH Version: older versions Platform: All URL: http://www.openssh.org/manual.html OS/Version: All Status: NEW Severity: enhancement

There is an amusing bug in ssh-add that causes it to go into an infinite loop. I am using openssh 1.2.3, and noticed that when I ran "ssh-add < /dev/null" in my X startup scripts, but didn't have ssh-askpass installed, ssh-add started spewing errors into my .xsession-errors and didn't stop. I found that what happens is: ssh-add forks and attempts to exec ssh-askpass. The

Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses

Damien, Here's a forwarded bug for you. Cheers, Phil. --[[message/rfc822]] Subject: Bug#52414: ssh-add uses ssh-askpass, but ssh doesn't Reply-To: David Huggins-Daines <dhd at plcom.on.ca>, 52414 at bugs.debian.org Resent-From: David Huggins-Daines <dhd at plcom.on.ca> Resent-To: debian-bugs-dist at lists.debian.org Resent-CC: Philip Hands <phil at hands.com>

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

Hi all, I have a script which calls ssh-add at a certain point, and I'm getting the following error: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory I don't see why it's doing this, since SSH_ASKPASS isn't set, and there should be a working terminal: SSH_ASKPASS If ssh needs a passphrase, it will read the passphrase from the