aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorAdam Weinberger <adamw@FreeBSD.org>2005-01-14 21:22:31 +0000
committerAdam Weinberger <adamw@FreeBSD.org>2005-01-14 21:22:31 +0000
commit1b0190a48e493770ef5fcf92b7d8fe60aabe543b (patch)
tree3c765a0115d6f49f4b71f1ac12a2b951ee5baf54 /UPDATING
parentf87e3e80b8c64792d11073ebb9f8eab44f535423 (diff)
downloadports-1b0190a48e493770ef5fcf92b7d8fe60aabe543b.tar.gz
ports-1b0190a48e493770ef5fcf92b7d8fe60aabe543b.zip
Notes
Diffstat (limited to 'UPDATING')
-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