linux-kernel - Re: How to verify linux-next

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]

Message-ID: <214615.1506942281@turing-police.cc.vt.edu>
Date:   Mon, 02 Oct 2017 07:04:41 -0400
From:   valdis.kletnieks@...edu
To:     Kamil Konieczny <k.konieczny@...tner.samsung.com>
Cc:     Pintu Kumar <pintu.ping@...il.com>, linux-kernel@...r.kernel.org,
        Damian Tometzki <damian.tometzki@...oud.com>,
        kernelnewbies@...nelnewbies.org
Subject: Re: How to verify linux-next

On Mon, 02 Oct 2017 10:11:34 +0200, Kamil Konieczny said:

> What about /usr/bin/ssh as init replacement ?

Well, if you are OK with your system panicking right away. :)

(Hint - the init process needs to be something that can run as a daemon).

If you use /usr/sbin/sshd, that has a *slightly* better chance of working,
except then you will need a *lot* of custom coding in your initramfs to do all
the system setup usually done by init during boot - mounting file systems,
configuring network interfaces, etc etc etc.  Plus, sshd probably doesn't have
some of the code needed for a true init process, such as reaping child
processes it didn't spawn itself, cleanly shutting down/rebooting, and so on...

Content of type "application/pgp-signature" skipped