From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
Cc: Discussion of Development and Customization of the Red Hat Linux
Installer
<anaconda-devel-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: RFC: writing kernel cmdline options to grub.conf for dracut
Date: Thu, 02 Jul 2009 19:18:48 +0200 [thread overview]
Message-ID: <4A4CEBF8.4010802@redhat.com> (raw)
In-Reply-To: <4A4CC19F.9020906-omB+W0Dpw2o@public.gmane.org>
On 07/02/2009 04:18 PM, Seewer Philippe wrote:
> Hans de Goede wrote:
>> Hi,
>>
>> This morning I've been talking to Harald Hoyer about what sort
>> of commandline options dracut will be needing to find the /
>> filesystem beside root=UUID=1234567890 .
>>
>> In most cases (normal disks, dmraid, mdraid, lvm, dmcrypt)
>> root=UUID=1234567890 should suffice.
>>
>> However in certain cases for example dracut will need additional
>> info to find the disks.
>>
>> We've come to the following plan for iscsi targets:
>> 1) Extend the dhcp_root dhcp variable iscsi syntax to
>> be able include a username password, so:
>> iscsi:192.168.50.2::::iqn.2009-06.dracut:target66
>> Can become:
>> iscsi:user:pass-Q0ErXNX1RuYrv4yRHWfJZg@public.gmane.org::::iqn.2009-06.dracut:target66
>> Or:
>> iscsi:user:pass:reverse_user:reverse_pass-Q0ErXNX1RuYrv4yRHWfJZg@public.gmane.org::::iqn.2009-06.dracut:target66
>>
>>
>> 2) Pass root-path=iscsi:... on the kernel cmdline, for each needed
>> iscsi target, so if
>> necessary this will be passed multiple times, dracut will be modified
>> to be able
>> handle multiple root-path arguments being passed in
>>
>> 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.
>
If a user has physical access to the machine, and the passwords are not encrypted
with some key which has to be entered manually (which would be really awkward for
say a headless server in a datacenter booting from an iSCSI SAN LUN) you've already
lost.
>>
>> 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?
Yes, in the case of machines booting of iSCSI it is, this is not a passphrase
for encryption, this is authentication information to connect to an iSCSI target
(one or more disks).
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-02 17:18 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
[not found] ` <4A4CC19F.9020906-omB+W0Dpw2o@public.gmane.org>
2009-07-02 17:18 ` Hans de Goede [this message]
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=4A4CEBF8.4010802@redhat.com \
--to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=anaconda-devel-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=philippe.seewer-omB+W0Dpw2o@public.gmane.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