| 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: <20080227185225.GB3137@nostromo.devel.redhat.com> Date: Wed, 27 Feb 2008 13:52:25 -0500 From: Bill Nottingham <notting@...hat.com> To: Randy Dunlap <randy.dunlap@...cle.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH, RFC, BAD IDEA] /proc/tty/console Randy Dunlap (randy.dunlap@...cle.com) said: > > I'm not seriously proposing this. But, as far as I can tell, this > > information isn't exposed to userspace anywhere, and it's a useful > > thing to know. I'm certainly open for better ideas on how to expose > > this (sysfs attributes? other?) > > > > .... > > > > The attached patch adds /proc/tty/console. The contents of it are > > simply a description of the current drivers attached to /dev/console. > > For example, a boot with 'console=ttyS3,115200n1 console=tty0' would > > yield: > > > > # cat /proc/tty/console > > unknown /dev/tty0 > > serial /dev/ttyS3 > > > > So it omits other consoles (non-tty) intentionally? > or does it include them even though the procfs filename contains "tty"? It only does consoles that have a tty_driver, as those are the ones I'd find most interesting. > Anyway, I'd like to see something like this. > Compare http://www.xenotime.net/linux/patches/consoles-list.patch > (April-2006). Reading that, unless I'm missing something, you'd lose the device name distinction (i.e., *which* serial port). Bill -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists