Displaying 20 results from an estimated 3000 matches similar to: "[Bug 1288] ssh-add on Cygwin -- can't access ssh-agent socket"
2007 Sep 14
1
[Bug 1288] ssh-add on Cygwin -- can't access ssh-agent socket
http://bugzilla.mindrot.org/show_bug.cgi?id=1288
Tom Ueltschi <bugzilla.mindrot.org at ueltschi.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla.mindrot.org at ueltsch
| |i.net
---
2004 Oct 04
1
BUG: ssh-agent unlinks sockets/files it doesn't own.
I've noticed a problem in the openssh sources. It can most easily be
replicated as follows:
> [rich at goblin] sl=1 ~
> 01:05:47$ ssh-agent -a ~/.ssh/agent.sock
> SSH_AUTH_SOCK=/home/rich/.ssh/agent.sock; export SSH_AUTH_SOCK;
> SSH_AGENT_PID=553; export SSH_AGENT_PID;
> echo Agent pid 553;
>
> [rich at goblin] sl=1 ~
> 01:05:50$ ssh-agent -a ~/.ssh/agent.sock
2003 Feb 19
0
[Bug 500] New: show how to start-up ssh-agent by default...
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:
2000 Oct 30
3
ssh-agent and ssh-add with openssh-2.2.0p1 on Redhat 7
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]$
2001 Feb 20
1
2.5.1p1 ssh-agent path problem in Solaris
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
2016 Jan 13
2
Re: v2v: error while killing ssh-agent after importing VM via xen+ssh
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
2006 Nov 02
0
SOLVED: Re: Using perl-Net-SSH-Perl with pubkey authentication under CGI.
On 02/11/06, Will McDonald <wmcdonald at gmail.com> wrote:
> Guys, I wonder if anyone can give me any pointers here, I hope it's
> CentOS related enough not to be too off topic, if it is then
> apologies.
Thanks to Marc and Ingimar for their suggestions, I think we've cracked it.
When Keychain runs it prompts the user for their private key password
then stores the
2008 Mar 05
1
Source keychain credentials in Perl?
Keychain is quite a useful tool for automating SSH logins without
having to use password-less keys:
http://www.gentoo.org/proj/en/keychain/
Normally it is used like this to set the SSH_AUTH_SOC and
SSH_AGENT_PID variables:
source ~/.keychain/hostname-sh
(This is what's in hostname-sh)
SSH_AUTH_SOCK=/tmp/ssh-XXn47DUn/agent.16721; export SSH_AUTH_SOCK;
SSH_AGENT_PID=16722; export
2014 Mar 02
1
ssh-askpass in bash script
Hey all,
I have ssh-askpass installed on Centos 5.7 and I'm trying to find a way to
log into the host and not have it ask me to enter in my long / complex
passphrase every time I ssh into another host.
I've googled for some scripts that you can add to your bash configuration
so that you won't have to do that.
So I have to end up typing 'eval $(ssh-agent) &&
2000 Dec 28
2
ssh-agent, protocol 2, openssh-2.3.0p1
Hi --
I saw an email on December 26th in the openssh-unix-dev mailing list
archived on MARC, indicating that agent forwarding is indeed not working
for 2.2, but that it is working for 2.3. That email referred to a user
with 2.3 clients and 2.2 server. I am running the 2.3 client AND server
and am having a similar problem. The only unusual aspect of my installation
is that I'm using port 24
2006 Dec 22
3
[Bug 1270] Public key (DSA) authentication works on 3.8p1 but not on 4.5p1
http://bugzilla.mindrot.org/show_bug.cgi?id=1270
Summary: Public key (DSA) authentication works on 3.8p1 but not
on 4.5p1
Product: Portable OpenSSH
Version: v4.5p1
Platform: HPPA
OS/Version: HP-UX
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: bitbucket at
2004 Aug 31
1
ssh / ssh-agent hang on exit
Hi :-)
we use ssh-agent, on exit it hangs
# ^D
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 15151 killed;
:-(
under OpenSSH_3.6.1p2 we have no problems with the agent.
Frank
client putty
OS Solaris8
_______________________________________________________
WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern
Informationen unter: http://freemail.web.de/?mc=021199
2006 Nov 22
1
sshd startup error on SCO SR6
Openssh 4.4p1 and 4.5p1
SCO Openserver 6 w/mp1, mp2
While installing v4.5p1, I noticed this sshd syslog error which began
appearing when I upgraded from v4.3p2 to v4.4p1:
Sep 1 17:54:41 tenzing sshd[12837]: error: Bind to port 22 on :: failed: \
Network is unreachable.
sshd -d reports:
debug1: Bind to port 22 on ::.
Bind to port 22 on :: failed: Network is unreachable.
debug1: Bind
2008 Jun 13
0
[Bug 1288] ssh-add on Cygwin -- can't access ssh-agent socket
https://bugzilla.mindrot.org/show_bug.cgi?id=1288
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker at zip.com.au
--- Comment #3 from Darren Tucker <dtucker at zip.com.au> 2008-06-14 09:20:37
2010 Apr 26
0
[Bug 1288] ssh-add on Cygwin -- can't access ssh-agent socket
https://bugzilla.mindrot.org/show_bug.cgi?id=1288
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm at mindrot.org
Status|NEW |RESOLVED
Resolution|
2011 Jan 24
0
[Bug 1288] ssh-add on Cygwin -- can't access ssh-agent socket
https://bugzilla.mindrot.org/show_bug.cgi?id=1288
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #5 from Damien Miller <djm at mindrot.org> 2011-01-24 12:33:43 EST ---
Move resolved bugs
2011 Jul 19
1
Re: Problem with Windows app accessing internet
OK, here's the diff file:
Code:
--- environment.before.reboot.txt 2011-07-19 17:43:58.200205228 +0100
+++ environment.after.reboot.txt 2011-07-19 17:53:07.549616184 +0100
@@ -1,16 +1,16 @@
ORBIT_SOCKETDIR=/tmp/orbit-charlie
-SSH_AGENT_PID=2912
+SSH_AGENT_PID=2337
TERM=xterm
SHELL=/bin/bash
-XDG_SESSION_COOKIE=2dd5655fe15f1c42f474dd204c45c6b6-1311075950.779608-828425652
2008 Jun 18
2
SSH connection hang after upgrade
I recently had to upgrade my version of OpenSSH from 4.7 to 5.0p1 on my
MacBook (Darwin). I installed the latest 'portable' tarball and
removed the system version:
$ ssh -V
OpenSSH_5.0p1, OpenSSL 0.9.7l 28 Sep 2006
$ which ssh
/usr/bin/ssh
sshd is the same version, installed in /usr/sbin/sshd. Now, things are
a bit broken: I am able to ssh from another machine into my MacBook,
so the
2016 Jan 13
0
Re: v2v: error while killing ssh-agent after importing VM via xen+ssh
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 setting the SSH_AGENT_PID environment), but I get the
> following error:
2003 Feb 24
9
[Bug 500] show how to start-up ssh-agent by default...
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