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
| ||
|
Message-ID: <eb11752c-7c20-2a39-d4a7-3be7282b4144@metux.net> Date: Fri, 12 Apr 2019 13:40:56 +0200 From: "Enrico Weigelt, metux IT consult" <lkml@...ux.net> To: "Adamski, Krzysztof (Nokia - PL/Wroclaw)" <krzysztof.adamski@...ia.com> Cc: Vincent Whitchurch <vincent.whitchurch@...s.com>, Greg KH <gregkh@...uxfoundation.org>, "jslaby@...e.com" <jslaby@...e.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] tty: Add NULL TTY driver On 12.04.19 09:30, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote: > Well, that depends. If the program doing those writes expects /dev/console > to be a tty device, then it cannot be any file. According to Vincent's mail, the actual problem is just systemd. Changing the kernel just for making one specific userland program (which happens to be written by somebody, who even doesn't know the semantics of rm -R) happy, sounds pretty strange for me. I'm not opposed to the general idea of having a dummy tty driver, but please for some actually sane usecases, not just working around broken userland :p --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists