From owner-freebsd-hackers Thu Apr 24 10:27:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA19103 for hackers-outgoing; Thu, 24 Apr 1997 10:27:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA19094 for ; Thu, 24 Apr 1997 10:27:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA01604; Thu, 24 Apr 1997 10:22:32 -0700 From: Terry Lambert Message-Id: <199704241722.KAA01604@phaeton.artisoft.com> Subject: Re: Best way to hook into user logins / logouts ? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 24 Apr 1997 10:22:32 -0700 (MST) Cc: davidn@labs.usn.blaze.net.au, msmith@atrad.adelaide.edu.au, abelits@phobos.illtel.denver.co.us, adrian@staff.psinet.net.au, freebsd-hackers@freebsd.org In-Reply-To: <199704241351.XAA27716@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 24, 97 11:21:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Personally, I think you're confusing "login" (gaining direct > > access to a system, or opening and entering a door) with > > "authentication" (the locks we put on the doors). > > > > But, as I said, it all depends on how you define things. > > Not really. I'm attempting to determine where the door(s) are so that > I can put locks on them. Or alternate locks. For "correct" code, given the currently accepted implementation methods, the "in" door is "login" and/or "login -f". The "out" door is "init", as it reaps a process which is a group leader which it inherited from "getty exec's login execs group leader". Why do you need an "out" door? If you decide you *really* can't live without some kind of "out" door, my recommendation is "login" forks instead of execs, and hangs around as the session manager, but not the process group leader. This requires a small change in the way signals like SIGHUP are propagated, and another small change in the way tcsetpgrp/tcgetpgrp operate in the way processes are "foregrounded". It also wants some changes to xdm, to either fully implement symmetry with "login", or to force it to go through "login" and establish the standard session manager as its "arbitrary program" ('man xdm' for details). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.