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

Date:   Mon, 02 Oct 2017 10:11:34 +0200
From:   Kamil Konieczny <k.konieczny@...tner.samsung.com>
To:     valdis.kletnieks@...edu, Pintu Kumar <pintu.ping@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Damian Tometzki <damian.tometzki@...oud.com>,
        kernelnewbies@...nelnewbies.org
Subject: Re: How to verify linux-next

On 29.09.2017 17:45, valdis.kletnieks@...edu wrote:
> On Fri, 29 Sep 2017 19:56:41 +0530, Pintu Kumar said:
> 
>> 1) If you have pointers on how to setup ssh/net connection on QEMU
>> with busybox, do let me know.
> 
> Busybox doesn't do that as far as I know, as it's intended as a single-user
> /sbin/init replacement. You'll need a full-featured userspace with an actual
> init daemon (sysvinit, systemd, etc) and an ssh daemon (openssh, or if you want [...]

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

-- 
Best regards,
Kamil Konieczny
Samsung R&D Institute Poland