I previously responded to a question about this bug, but didn't CC the bug, so I'm forwarding this now.
Justin On Sat, Dec 18, 2004 at 07:47:10PM -0500, pryzbyj wrote: > I don't know if I've ever done this myself, but, reportedly, telinit 1 > over ssh *will* go into single user mode, but will also kick off the > root user. That's bad; potentially, the user *thought* they could run > single-user over ssh. So, I propose that telinit (aka init) check > that /proc/self/fd/0 => (whatever it should be) so that it is always a > local user. > > If the ssh user runs telinit 1, warn them and do nothing. If they > also specify --force, then actually go into single user mode and kick > them off ssh. > > Justin > > On Sun, Dec 19, 2004 at 12:38:41AM +0000, Miquel van Smoorenburg wrote: > > On Sat, 18 Dec 2004 02:34:46, Justin Pryzby wrote: > > >Package: sysvinit > > >Version: 2.86-5 > > >Severity: normal > > > > > > > > >telinit 1 over ssh will potentially do something bad. > > > > What exactly do you mean, "bad" ? > > > > >Other than > > >implementing a remote single-user-mode, I hope that the current single > > >user mode would stop the user from screwing up. > > > > Screw up what ? > > > > And why do you want a --force ? Please clarify. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
