From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/902 Path: news.gmane.org!not-for-mail From: aep Newsgroups: gmane.linux.lib.musl.general Subject: Re: make -i with linux-pam Date: Tue, 22 May 2012 20:22:58 +0200 Message-ID: References: <20120513205824.16f08160@newbook> <20120514041106.GS163@brightrain.aerifal.cx> <20120514170931.5ebe58cf@newbook> <20120516032449.GU163@brightrain.aerifal.cx> <77353a536cf4831c07f838aa74905e7c@exys.org> <20120521192859.GG163@brightrain.aerifal.cx> <4da7637098a099e65cafb69a43dec4f0@exys.org> <87obpgkvkp.fsf@gmail.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1337710869 31783 80.91.229.3 (22 May 2012 18:21:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 22 May 2012 18:21:09 +0000 (UTC) To: Original-X-From: musl-return-903-gllmg-musl=m.gmane.org@lists.openwall.com Tue May 22 20:21:08 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1SWthi-00061O-OT for gllmg-musl@plane.gmane.org; Tue, 22 May 2012 20:21:06 +0200 Original-Received: (qmail 19905 invoked by uid 550); 22 May 2012 18:21:06 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 19897 invoked from network); 22 May 2012 18:21:06 -0000 In-Reply-To: <87obpgkvkp.fsf@gmail.com> X-Sender: aep@exys.org User-Agent: Roundcube Webmail/0.5.4 Xref: news.gmane.org gmane.linux.lib.musl.general:902 Archived-At: On Tue, 22 May 2012 18:51:50 +0200, Christian Neukirchen wrote: > A bit OT: I realize utmp has major flaws, but the feature itself > (seeing > which users are logged in) I consider useful, That ... actually is the flaw. > for machines with more > than one user. How else can that be done? If your requirements are identical to utmp (only one possible login mechanism, compromising user privacy is intended), then utmp is the way to go. What's from the 60s, is just cramming it into libc and giving John Doe write access for logging his lunch times. Which is why i argued not to make it a stub, but instead fail compiling and let users figure out where to get a logwtmp from (maybe even submitting it upstream to pam!) People actually using PAM, will probably also want "who" to work, and if pam is the god given login system on your machine, then there's nothing wrong with giving it exclusive utmp access.