From: "Diego Petteno (flameeyes)" <flameeyes@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/base/pam: upgrade-0.99.xml
Date: Thu, 22 Nov 2007 21:24:40 +0000 [thread overview]
Message-ID: <E1IvJXM-0006Ab-Ku@stork.gentoo.org> (raw)
flameeyes 07/11/22 21:24:40
Modified: upgrade-0.99.xml
Log:
Update the information about pam_console, as it's now masked for
removal and thus no more available for users to install separately.
Revision Changes Path
1.11 xml/htdocs/proj/en/base/pam/upgrade-0.99.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml?r1=1.10&r2=1.11
Index: upgrade-0.99.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- upgrade-0.99.xml 1 Nov 2007 13:51:22 -0000 1.10
+++ upgrade-0.99.xml 22 Nov 2007 21:24:40 -0000 1.11
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v 1.10 2007/11/01 13:51:22 flameeyes Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/pam/upgrade-0.99.xml,v 1.11 2007/11/22 21:24:40 flameeyes Exp $ -->
<guide link="/proj/en/base/pam/upgrade-0.99.xml" lang="en">
<title>Linux-PAM 0.99 upgrade guide</title>
@@ -18,8 +18,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.6</version>
-<date>2007-11-1</date>
+<version>1.7</version>
+<date>2007-11-22</date>
<chapter>
<title>Upgrade guide</title>
@@ -138,8 +138,8 @@
Additionally, the <b>berkdb</b> USE flag, used to build the <c>pam_userdb</c>
module was removed; in its stead you will have to manually merge the
<c>sys-auth/pam_userdb</c> package that provides the module with the same name.
-The same goes for <b>pam_console</b>, although this one is also deprecated; see its
-own section for more details.
+Also the <b>pam_console</b> USE flag was removed, and the module is no longer
+available, please see this in its own section.
</p>
<p>
@@ -157,23 +157,25 @@
<p>
The <c>pam_console</c> module was designed by RedHat to allow setting different
permissions on devices for users logging in via hardware access (either in X
-through the various graphical login applications, or through the console login).
-This approach caused more than a few problems in the past with users unable to
-get their devices working, and was then disabled by default, linked to a
-<b>pam_console</b> USE flag for those needing it.
+through the various graphical login applications, or through the console
+login).This approach caused more than a few problems in the past with users
+unable to get their devices working, and was then disabled by default, linked to
+a <b>pam_console</b> USE flag for those needing it.
</p>
<p>
As of version 0.99 of Linux-PAM the whole RedHat patchset was dropped.
-<c>pam_console</c> is no longer shipped with the main package; for the people
-needing it, it's available in <c>sys-auth/pam_console</c>, although the need for
-this is being reduced gradually, as HAL switched to a
-<c>pam_consolekit</c>-based approach (in <c>sys-auth/consolekit</c>).
+<c>pam_console</c> is no longer shipped with this package. Although for a while
+available as <c>sys-auth/pam_console</c> for those needing it, a <uri
+link="http://bugs.gentoo.org/show_bug.cgi?id=199193">security bug</uri> forced
+the masking and removal of this package.
</p>
<p>
-Nothing more than using <c>sys-auth/pam_console</c> is required for users
-needing this module.
+The need for <c>pam_console</c> is being mitigated by HAL switching to
+ConsoleKit as alternative. Those still needing a behaviour similar to
+pam_console's are invited to update their code so that ConsoleKit can be used
+instead, or use a <b>plugdev</b> group together with <c>pam_group</c> module.
</p>
</body>
--
gentoo-commits@gentoo.org mailing list
next reply other threads:[~2007-11-22 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 21:24 Diego Petteno (flameeyes) [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 17:50 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/base/pam: upgrade-0.99.xml Diego Petteno (flameeyes)
2008-02-24 22:16 Diego Petteno (flameeyes)
2008-02-24 20:28 Diego Petteno (flameeyes)
2007-11-01 13:51 Diego Petteno (flameeyes)
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=E1IvJXM-0006Ab-Ku@stork.gentoo.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.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