linux-kernel - Re: [PATCH v2 0/1] Allow setting hostname before userspace starts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri,  6 May 2022 09:44:20 -0600
From:   Dan Moulding <dmoulding@...com>
To:     pavel@....cz
Cc:     akpm@...ux-foundation.org, corbet@....net, dmoulding@...com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        tglx@...utronix.de
Subject: Re: [PATCH v2 0/1] Allow setting hostname before userspace starts

On May 6, 2022, at 1:23 AM, Pavel Machek <pavel@....cz> wrote:

> init gets passed command line parameters kernel did not use. So init
> can do that easily.

I agree this is a problem that *can* be delegated to init to solve.
But is it *better* to do that? Why have the kernel pass the the hostname
to the init system, just so that the init system has to pass it back to the
kernel later?

> Plus, there's initrd.

This to me is a reason why it's better for the kernel to do this. If left up
to the init system, it must be sure it gets done correctly both when an
initramfs is used, and when one is not.

P.S. Apologies to anyone who received this twice, my first reply was
bounced by the list servers.

Cheers,

  -- Dan