aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoradamw <adamw@FreeBSD.org>2005-01-15 05:22:31 +0800
committeradamw <adamw@FreeBSD.org>2005-01-15 05:22:31 +0800
commit15a817ada4d653b91c7d5efafb1276ffefa52682 (patch)
tree0bd085d0e364d6e90434307774001b05094763bf
parent18f56441bb7d5f3f8ccf1649bdc0f506ed9d8e37 (diff)
downloadfreebsd-ports-gnome-15a817ada4d653b91c7d5efafb1276ffefa52682.tar.gz
freebsd-ports-gnome-15a817ada4d653b91c7d5efafb1276ffefa52682.tar.zst
freebsd-ports-gnome-15a817ada4d653b91c7d5efafb1276ffefa52682.zip
Add an entry instructing people to remove an unintentionally-created
/etc/pam.d directory, which causes lockouts on 4.x.
-rw-r--r--UPDATING19
1 files changed, 19 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index c1c2b2bb12fd..f6669f6058ed 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,25 @@ You should get into the habit of checking this file for changes each
time you update your ports collection, before attempting any port
upgrades.
+20050114:
+ AFFECTS: users of security/libgnomesu, esp. on FreeBSD 4.x.
+ AUTHOR: adamw@FreeBSD.org
+
+ If you installed libgnomesu the day it was added to the ports tree,
+ you have a malformed PAM control file in /etc/pam.d/. All libgnomesu
+ users should remove /etc/pam.d/gnomesu-pam, and 5.x users should
+ replace it with the version in the updated libgnomesu port (ensure
+ that you're using the most current revision of the libgnomesu port).
+
+ 4.x users: listen up! The presence of the /etc/pam.d/ directory (and
+ anything in that directory) presents a Very Bad Thing. Unless you've
+ manually tweaked your PAM settings, you must run:
+
+ # rm /etc/pam.d/gnomesu-pam
+ # rmdir /etc/pam.d/
+
+ or all users will be locked out of your system!
+
20050110:
AFFECTS: users of irc/iip
AUTHOR: lioux@FreeBSD.org