From: Harald Hoyer <harald@redhat.com>
To: Seewer Philippe <philippe.seewer@bfh.ch>
Cc: initramfs@vger.kernel.org,
Discussion of Development and Customization of the Red Hat Linux
Installer <anaconda-devel-list@redhat.com>
Subject: Re: RFC: writing kernel cmdline options to grub.conf for dracut
Date: Thu, 02 Jul 2009 17:09:31 +0200 [thread overview]
Message-ID: <4A4CCDAB.60102@redhat.com> (raw)
In-Reply-To: <4A4CC19F.9020906@bfh.ch>
On 07/02/2009 04:18 PM, Seewer Philippe wrote:
> Hans de Goede wrote:
>> 3) chmod /proc/cmdline 400, so that it cannot be read by ordinary
>> users, plugging
>> the passwork leak problem
>
> This does not really plug the leak. Just boot until initramfs is loaded,
> pull the network plug and wait until dracut drops us to a (root-)shell.
Ah, which reminds me, that we should have an option to turn that off.
>
>>
>> Now the remaining question is how to implement the adding of the needed
>> cmdline options to grub.conf.
>
> Question: Is it really necessary to provide username/password to dracut?
> Wouldn't it be better to ask the user? I mean if a mount is password
> protected, be it cryptroot, nfs4 or whatever, shouldn't the user enter
> the data?
>
username/password for iSCSI disks entered by a normal user every day he boots
his diskless client?
next prev parent reply other threads:[~2009-07-02 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 11:10 RFC: writing kernel cmdline options to grub.conf for dracut Hans de Goede
[not found] ` <4A4B4443.50503-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-02 14:18 ` Seewer Philippe
2009-07-02 15:09 ` Harald Hoyer [this message]
[not found] ` <4A4CC19F.9020906-omB+W0Dpw2o@public.gmane.org>
2009-07-02 17:18 ` Hans de Goede
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=4A4CCDAB.60102@redhat.com \
--to=harald@redhat.com \
--cc=anaconda-devel-list@redhat.com \
--cc=initramfs@vger.kernel.org \
--cc=philippe.seewer@bfh.ch \
/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