public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] PAM related: pam_console ?
Date: Wed, 06 Apr 2005 23:40:50 +0200	[thread overview]
Message-ID: <1112823650.9136.94.camel@nosferatu.lan> (raw)
In-Reply-To: <200503311517.10772@enterprise.flameeyes.is-a-geek.org>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

On Thu, 2005-03-31 at 15:17 +0200, Diego "Flameeyes" Pettenò wrote:
> Seems like pam_console modules is broken. I'm not able to make it compile both 
> as a standalone ebuild i'm trying to write and as the complete pam with 
> +pam_console flag.
> 
> Anyway I was wondering what pam_console is used for, at the end. It's a way to 
> set up permissions when someone logins at a console. I would never use 
> something like that on a remote server, as anyone which could have a local 
> login can do anything· It also doesn't make sense on a recent user system 
> configured properly, as devfs/udev would take care of permissions, and users 
> needs only to set the group correctly (simpler than using pam_console 
> anyway).
> 
> Seems to me like a workaround for old old (too old!) systems, which is no more 
> needed at least for us.
> 
> I know this is there also for compatibility, but this makes sys-libs/pam 
> ebuild very bloated as for now, and still I don't know a reason to have it 
> there.
> 
> Some comments about it?

/care

We anyhow move to not using it by default in 0.78 - axe it while we
still can.


-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-04-06 21:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 13:17 [gentoo-dev] PAM related: pam_console ? Diego "Flameeyes" Pettenò
2005-03-31 13:27 ` Mike Frysinger
2005-03-31 13:34   ` Diego "Flameeyes" Pettenò
2005-03-31 13:57     ` Mike Frysinger
2005-03-31 14:26       ` Diego "Flameeyes" Pettenò
2005-03-31 15:01         ` Mike Frysinger
2005-03-31 15:17           ` Diego "Flameeyes" Pettenò
2005-04-06 21:47         ` Martin Schlemmer
2005-04-07  7:34           ` [gentoo-dev] bootstrap.sh and /var/lib/portage/world mathias
2005-04-07 13:08             ` Chris Gianelloni
2005-04-06 21:41   ` [gentoo-dev] PAM related: pam_console ? Martin Schlemmer
2005-03-31 20:38 ` Robin H. Johnson
2005-03-31 21:09   ` Diego "Flameeyes" Pettenò
2005-03-31 21:35     ` Mike Frysinger
2005-03-31 22:19       ` Diego "Flameeyes" Pettenò
2005-04-06 21:52         ` Martin Schlemmer
2005-04-06 21:40 ` Martin Schlemmer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1112823650.9136.94.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox