On Fridayen den 2 August 2002 11.33, Borsenkow Andrej wrote: > > On Thu Aug 01, 2002 at 03:16:35PM +0200, Oden Eriksson wrote: > > > > [...] > > > > > > > > > Disable privsep is another way to do it. > > > > > > > > > > > > that means that sshd in default installation has large bug. If > > > > > > > > privsep > > > > > > > > > > results in complete user lockout, then _PLEASE_ disable it by > > > > > > > > default. > > > > > > > > > True, and this has been discussed earlier IIRC. > > > > > > > > Unfortunately disabling privsep still does not wotk. Now it fails > > > > differently but still fails, at lest when using the same openssh > > > > client > > > > > > version. May be there is something else that must be changed? > > > > > > Hmmm, I thought this was only a server side thing... Does your > > > > sshd_config > > > > > look like this "UsePrivilegeSeparation no" on the server, and (silly > > > question) have you restarted the sshd (stop|start)?. > > > > Right. privsep is only useful server-side. > > I have disabled it on server side. And I have restarted server after it. > With privsep enabled it fails differently (just closes connection with > different messages logged).
What happens if you compile the client without privsep? -- Regards // Oden Eriksson Deserve-IT Networks -> http://d-srv.com
