Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
No idea - however - it would be important to note what Cygwin dll you upgraded from, and lookup the date it was originally released. I would check the Cygwin release notes since that point. In the past I was bit by Cygwin security and simply upgrading my Cygwin install -- the ssh server stopped working. For my problem, the cause was a change to Cygwin security, where the the NT security model was imported into the system. This is all very vague I know, but perhaps the newer version enabled or tightened security so your old configuration is no longer acceptable. Check the Cygwin User Guide, particularly under the CYGWIN environment variable and "ntsec". This was where I fixed my win2k sshd server problem some time back. ----- Original Message ----- From: "jbk" <jbk at mail2.gis.net> To: "Blu" <discuss at blu.org> Sent: Thursday, April 24, 2003 7:08 AM Subject: ssh-add > I have been useing ssh under cygwin to access my > Linux server from Wnt4sp5. I have been using > successfuly the following script to initiate my > ssh session. > > ################################## > #!/bin/bash > # startagent > # Purpose of this script is to start ssh-agent > # This script is from John Abreau @blu.org who > # runs it from the command line > > ssh-agent | head -2 > /home/Dad/.ssh/agent-id > sleep 3 > source .ssh/agent-id > ssh-add > # end of script 021201 > ############################ > > I recently upgraded to the latest cygwin dll > 1.3.22-1 and the 4/1/03 update of openssh via the > cygwin setup utility. Now when I run this script I > get the following mssg: > Could not open a connection to your > authentication agent. > > There is a PID for ssh-agent when I type ps. I > have run this script from the command line one > step at a time (excluding sleep 3) and it is when > ssh-add is entered that I get the error mssg. I > can still type $> ssh username at server or if I am > in an Xsession $> ssh -X username at server and log > into the Linux server. > > Has anyone run into this problem? > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |