From: Corinna Vinschen <corinna@vinschen.de>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: "'Cygwin mailing list" <cygwin@sourceware.cygnus.com>
Subject: Re: BASH and OpenSSH problems
Date: Wed, 31 May 2000 04:21:00 -0000 [thread overview]
Message-ID: <3934F4D1.34637F01@vinschen.de> (raw)
In-Reply-To: <200005311055.MAA07817@cerbere.u-strasbg.fr>
Pierre Muller wrote:
>
> I am trying to use ssh-agent for Corrina's latest port
> with bash 2.04.
>
> I am working on a Win95 machine and I also installed crypt and login package
> as recommended.
???
I never mentioned that crypt and login are needed to
work with ssh. They are needed for the inetutils package.
> Using ssh-agent does not set the SSH_AUTH_SOCK and
> SSH_AGENT_PID env variables !
>
> Do I miss something here ??
Definitely. When you start ssh-agent, you'll have to redirect
it's output to `eval' to get it working. ssh-agent only writes
the environment settings to stdout. The same is true for
`ssh-agent -k'.
Furthermore ssh-agent has no initial private keys. You'll have
to add them using `ssh-add' after starting ssh-agent. You can get
it a bit more convenient with an alias, eg.:
alias startssh='eval `ssh-agent`; ssh-add'
alias stopssh='eval `ssh-agent -k`'
or by doing that in your profile.
> Even worse at exit of BASH, ssh-agent is not being killed and
> I need to kill it with Crtl-Alt-Suppr :(
>
> Is this a known bug ?
No, it's the way described above and it's intentionally.
Corinna
--
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-05-31 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 19:40 cygwin Dietmar Lettau
2000-05-31 0:48 ` cygwin Heinz-Juergen Oertel
2000-05-31 3:38 ` BASH and OpenSSH problems Pierre Muller
2000-05-31 4:21 ` Corinna Vinschen [this message]
2000-05-31 5:19 ` Pierre Muller
2000-05-31 6:51 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3934F4D1.34637F01@vinschen.de \
--to=corinna@vinschen.de \
--cc=cygwin@sourceware.cygnus.com \
--cc=muller@cerbere.u-strasbg.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).