public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: baselayout changes for livecds
Date: Sat, 17 Jan 2004 22:23:40 +0200	[thread overview]
Message-ID: <1074371020.8472.1.camel@nosferatu.lan> (raw)
In-Reply-To: <200401171929.06293.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

On Sat, 2004-01-17 at 20:29, Paul de Vrieze wrote:
> On Saturday 17 January 2004 18:06, Brad House wrote:
> > no, the rcscripts must now parse the kernel commandline opts
> > to get a few options. There's really not many other ways to
> > do it.  Besides you just proved by your statement that someone
> > could instead pass   init=/bin/sh  and override any sort of
> > init process, so trying to make the 'cdroot' option secure
> > is obsurd, as there's 10 million other ways to get in if you
> > have direct access to the computer.
> 
> The big difference is that init=/bin/sh does not give you a normal working 
> system, cdboot however could be abused to get a normal functioning 
> passwordless console. That would allow incapable systemadmins to decide to do 
> this, or even tell others to do it (the latter I want to prevent).
> 

I _did_ say it already, but you apparently did not want to listen - the
kernel opts is not needed, as there is no need to be dynamic.  Its
either a livecd or not.  And as Paul did mention, it might be open for
exploit, although 'init=/bin/bash' will work as well.

The baselayout ebuild will be modified to do changes if USE=livecd, as
it is sane, and I imagine some other things will need special livecd
tweaking as well.  Meaning, if USE=livecd, pkg_postinst() will
'echo CDBOOT=1 >> ${ROOT}/etc/rc.conf', and do whatever else.


Thanks,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-17 20:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17  4:23 [gentoo-releng] baselayout changes for livecds Brad House
2004-01-17 10:26 ` [gentoo-releng] " Paul de Vrieze
2004-01-17 16:28   ` Brad House
2004-01-17 16:51     ` Pieter Van den Abeele
2004-01-17 17:06       ` Brad House
2004-01-17 17:34         ` Pieter Van den Abeele
2004-01-17 18:29         ` Paul de Vrieze
2004-01-17 20:23           ` Martin Schlemmer [this message]
2004-01-17 20:57             ` Brad House
2004-01-18  8:06           ` Martin Schlemmer
2004-01-17 22:11 ` Martin Schlemmer
2004-01-17 22:32   ` John Davis
     [not found]     ` <1074380018.8472.9.camel@nosferatu.lan>
2004-01-18  5:24       ` Daniel Robbins
2004-01-18  8:24         ` Martin Schlemmer
2004-01-18 16:42           ` Brad House
2004-01-18 17:30             ` Martin Schlemmer
2004-01-18 17:40               ` Brad House
2004-01-18 17:34             ` Martin Schlemmer
2004-01-19 21:39               ` Daniel Robbins
2004-01-19 21:47                 ` Brad House
2004-01-20  4:40                 ` Martin Schlemmer
2004-01-20 19:20                   ` Daniel Robbins
2004-01-21 19:12                     ` Martin Schlemmer
2004-01-23 18:07                       ` Martin Schlemmer
2004-01-18  0:47   ` Daniel Robbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1074371020.8472.1.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox