Re: McAfee and CygWin SSH

Nico Kadel-Garcia wrote:
Darren Tucker wrote:
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.

OK, that worked. So it looks like's definitely happening at the re-exec,
darn it. I'm not familiar enough Windows internals to get into this, and my
raw SSH coding is pretty rusty. Any ideas other than "run it from inetd"?

In the meantime, I'm gonna rip out McAfee by the roots and see if that
helps.



Can't you just tell McAfee that the ssh executable is allowed to do
whatever it wants? (Assuming this is a MacAfee FW issue)
.

Relevant Pages