linux-kernel - Re: VT-less kernels, and /dev/console on x86

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: <6066116.alqRGMn8q6@nerdopolis2>
Date: Sun, 18 Aug 2024 10:33:46 -0400
From: nerdopolis <bluescreen_avenger@...izon.net>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: pmladek@...e.com, rostedt@...dmis.org, john.ogness@...utronix.de,
 senozhatsky@...omium.org, tglx@...utronix.de, tony@...mide.com,
 linux-kernel@...r.kernel.org, Bagas Sanjaya <bagasdotme@...il.com>
Subject: Re: VT-less kernels, and /dev/console on x86

On Sunday, August 18, 2024 1:12:58 AM EDT Greg KH wrote:
> On Sat, Aug 17, 2024 at 10:31:17PM -0400, nerdopolis wrote:
> > The thought is that when distributions eventually decide to go VT-less they are
> > not going to want to change the kernel boot options in the bootloader config to
> > force console=ttynull, and might want this to happen automatically.
> 
> If/when they want to do this, odds are a command line will be fine, or
> they will build in ttynull properly into their kernels.
> 
For new installs, I guess it would be fine, but for existing installs they
would have to script out the changes to /etc/default/grub, and/or however
systemd-boot handles default kernel command line arguments during the upgrade
process.

I couldn't get ttynull to be selected by default without the command line
without the console=ttynull, even when building it into the kernel (not as a
module) without the modification to printk.c
> thanks,
> 
> greg k-h
>