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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220506072322.GA3925@amd>
Date:   Fri, 6 May 2022 09:23:23 +0200
From:   Pavel Machek <pavel@....cz>
To:     Dan Moulding <dmoulding@...com>
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        tglx@...utronix.de, akpm@...ux-foundation.org, corbet@....net
Subject: Re: [PATCH v2 0/1] Allow setting hostname before userspace starts

Hi1

> Some userspace processes may rely on gethostname to always return the
> correct machine name. However, the only way that the hostname may be
> set is by some other userspace process calling sethostname
> first. During boot, if a process that depends on gethostname runs
> before sethostname has been called, then the process that called
> gethostname is going to get an incorrect result.

Don't do that, then? :-).

init gets passed command line parameters kernel did not use. So init
can do that easily. Plus, there's initrd.

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)