Bug#345741: Would a restricted form of the INIT_PROG feature suffice?

2006-01-17 Thread Dana How
a re-exec, so if you did a second "telinit u" after running the script below then /etc/init would be re-exec'ed. I don't know if this NOT/IS inconsistency is a feature or a defect. Thanks for helping me with this problem. I hope our conversation can be easily found by any

Bug#345741: Would a restricted form of the INIT_PROG feature suffice?

2006-01-12 Thread Dana How
On 1/12/06, Thomas Hood <[EMAIL PROTECTED]> wrote: > Dana How wrote: > > Let me know what you think of it. > Your unionfs scenario leads me to ask this: why not just bind mount a > different program on top of /sbin/init and do "telinit u"? That is, to switch from

Bug#345741: Would a restricted form of the INIT_PROG feature suffice?

2006-01-12 Thread Dana How
On 1/12/06, Dana How <[EMAIL PROTECTED]> wrote: > On 1/12/06, Thomas Hood <[EMAIL PROTECTED]> wrote: > > I have an idea. Instead of allowing an arbitrary program path to be set, > > we allow > > a _suffix_ to be set. "telinit -e INIT_SFX=foo ; telinit u&quo

Bug#345741: Would a restricted form of the INIT_PROG feature suffice?

2006-01-12 Thread Dana How
On 1/12/06, Thomas Hood <[EMAIL PROTECTED]> wrote: > I have an idea. Instead of allowing an arbitrary program path to be set, we > allow > a _suffix_ to be set. "telinit -e INIT_SFX=foo ; telinit u" would cause init > to exec > "/sbin/init.foo". Now, /sbin/init.foo can be a symlink to an execu

Bug#345904: ldd $(which bash) shows fewer libs than bash -c 'lsof -p $$'

2006-01-03 Thread Dana How
Package: libc6 Version: 2.3.5 Compare these two reports: % ldd $(which bash) linux-gate.so.1 => (0xe000) libncurses.so.5 => /lib/libncurses.so.5 (0xb7f85000) libdl.so.2 => /lib/tls/libdl.so.2 (0xb7f81000) libc.so.6 => /lib/tls/libc.so.6 (0xb7e49000) /l

Bug#345741: Please add INIT_PROG env var to override re-exec'ing from /sbin/init

2006-01-03 Thread Dana How
On 1/3/06, Thomas Hood <[EMAIL PROTECTED]> wrote: > Petter Reinholdtsen wrote: > > This sounds like a security issue. If the admin made / read-only, and > > someone is able to gain enough privileges to talk to init but not to > > remount the file system, they could re-exec init with a binary they

Bug#345741: Please add INIT_PROG env var to override re-exec'ing from /sbin/init

2006-01-03 Thread Dana How
Package: sysvinit Version: 2.86.ds1-6 The "telinit u" feature can be used to re-exec /sbin/init, useful if you've just rewritten (re-installed) /sbin/init. However, if /sbin/init is on a read-only filesystem, or you want to redirect init to be running from a different filesystem because you need

Bug#345719: Please remove pointless runlevel restriction on telinit u

2006-01-02 Thread Dana How
Package: sysvinit Version: 2.86.ds1-6 Around Feb 1998, the "telinit u" feature was added to the sysvinit package. This allowed a running /sbin/init to be updated (re-executed after re-installing). There are other situations where it would be useful to re-exec /sbin/init . Midway through a boot fr