Re: McAfee and CygWin SSH
- From: Darren Tucker <dtucker@xxxxxxxxxxxxxxxx>
- Date: 17 Aug 2006 12:17:05 GMT
On 2006-08-17, Nico Kadel-Garcia <nkadel@xxxxxxxxxxx> wrote:
And I see this on the server side:
$ /usr/sbin/sshd -d
debug1: sshd version OpenSSH_4.3p2
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: fd 4 clearing O_NONBLOCK
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
This is the point where sshd re-execs itself to handle the new connection.
I suspect that this is failing for because of some change that occurred
when you installed the software (PATH, maybe?)
You can prevent the re-exec by adding "-r" to sshd's command line.
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
.
- Follow-Ups:
- Re: McAfee and CygWin SSH
- From: Nico Kadel-Garcia
- Re: McAfee and CygWin SSH
- References:
- McAfee and CygWin SSH
- From: Nico Kadel-Garcia
- Re: McAfee and CygWin SSH
- From: Nico Kadel-Garcia
- Re: McAfee and CygWin SSH
- From: Todd H.
- Re: McAfee and CygWin SSH
- From: Nico Kadel-Garcia
- Re: McAfee and CygWin SSH
- From: Richard E. Silverman
- Re: McAfee and CygWin SSH
- From: Nico Kadel-Garcia
- McAfee and CygWin SSH
- Prev by Date: Re: McAfee and CygWin SSH
- Next by Date: Re: McAfee and CygWin SSH
- Previous by thread: Re: McAfee and CygWin SSH
- Next by thread: Re: McAfee and CygWin SSH
- Index(es):
Relevant Pages
|