Date: Thu, 1 Oct 2015 17:21:19 -0400 (EDT) From: Garrett Wollman <wollman@hergotha.csail.mit.edu> To: jilles@stack.nl Cc: arch@freebsd.org Subject: Re: login -f changing session getlogin(2) Message-ID: <201510012121.t91LLJ9h025117@hergotha.csail.mit.edu> References: <20151001203436.GA22737@stack.nl> <560D826D.7000302@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20151001203436.GA22737@stack.nl>, jilles@stack.nl writes: >I think the supposed use case for login -f is a remote login daemon that >handles authentication by itself but wants to delegate account and >session functionality. Indeed, sshd has UseLogin, but it is rarely used >and discouraged. Historically, as I remember it, "login" was a shell built-in that was effectively an alias for "exec login". It may still be that way in antique csh. The assumption from time immemorial is that if login exits, the parent process will not distinguish it from any other logout, so login is permitted to overwrite persistent session state. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201510012121.t91LLJ9h025117>