Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ssh-add



Thanks, I tried that and got the same response. I think the problem has to
do with a change in the way cygwin has implimented their latest version of
ssh. I have their documentation and it does indicate a change.

Derek Martin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Apr 24, 2003 at 07:08:27AM -0400, jbk wrote:
> > 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.
>
> I've never seen your problem, but I don't start ssh-agent that way
> either.  Try typing this on the command line (in a bash window, not in
> a cmd.exe window) instead:
>
>   $ eval `ssh-agent`; ssh-add
>
> See if that makes any difference.  I doubt it will, but I s'pose it
> could.  You need to do this from bash, because eval is a bash built-in
> command.  Since you just upgraded stuff, I'd be inclined to think that
> you didn't upgrade a library that ssh depends on, resulting in an
> incompatibility.  But it's hard to say...
>
> - --
> Derek D. Martin
> http://www.pizzashack.org/
> GPG Key ID: 0xDFBEAD02
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+qNd/HEnASN++rQIRAqPRAKCZ/SGmzAQAoAe/cz9jmq25GM9WJACghOdn
> s7LV4ELf/Ie7seywFSC6FVw=
> =otmW
> -----END PGP SIGNATURE-----
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org