Subject: Re: Privsep question: can the slave's child make monitor calls? - msg#00399
List: network.openssh.devel
Niels Provos wrote:
>
On Wed, Jan 29, 2003 at 12:49:22PM +0100, Markus Friedl wrote:
>
> no, i think (e) should _not_ talk to the monitor.
>
Those descriptors are all close on exec.
The situation I was describing was sshd deliberately calling a monitor
function after the fork but before the exec.
I suspect Markus is right and I shouldn't do that, in which case I need
to figure out another way to solve my problem.
--
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.
Was this page helpful?
Thread at a glance:
Next Message by Date:
click to view message preview
Snapshots not updating?
Is there a problem with the snapshots? The newest one on
ftp.ca.openbsd.org is a week old.
-Daz.
--
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.
Next Message by Thread:
click to view message preview
PermitRootLogin=yes no longer lets root login
Hi All,
While testing another patch, I found that I could not longer log in as
root, even if PermitRootLogin was yes. It seems to be the following
code in auth_password:
$ cvs diff -r1.48 -r1.49 auth-passwd.c
[snip]
#ifndef HAVE_CYGWIN
- if (pw->pw_uid == 0 && options.permit_root_login != PERMIT_YES)
+ if (pw->pw_uid == 0 && options.permit_root_login !=
PERMIT_NO_PASSWD)
return 0;
#endif
[snip]
Was this intentional?
-Daz.
--
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.