linux-kernel - Re: design of screen-locks for text-mode sessions

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: <Pine.LNX.4.61.0609111259000.14498@yvahk01.tjqt.qr>
Date:	Mon, 11 Sep 2006 13:01:34 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	"Travis H." <solinym@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: design of screen-locks for text-mode sessions

>
> This may diverge away from kernelspace, and if so I'll take the discussion
> off-list with interested parties.  In the meantime, I was wondering what people
> thought about the best design for locking text-mode console sessions.  It's a
> checkbox on some regulatory compliance list, I think for the PCI specs (that's
> credit cards, not the bus) and I'm sort of surprised there isn't an
> easy-to-find
> package for this.

screen. Start it. Hit ^A^X. Does not support autolocking though.

> Am I correct in assuming that login execs the shell, as opposed to
> hanging around
> after authentication?

Login waits for its subprocess to terminate. However, not every 'system' 
uses login, e.g. ssh.


Jan Engelhardt
-- 
-
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/