diff --git a/ChangeLog b/ChangeLog
index 8a856e309..3f155f796 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -64,6 +64,8 @@
 	* testsuite/Makefile.in testsuite/README testsuite/testfile.pnm:
 	  Changed testsuite to use the test backend instead of the pnm
 	  backend. This actually works with current sane-backends.
+	* PROBLEMS: Removed pnm problem description. It's not relevant for
+	  normal users and explained in the sane-pnm man page anyway.
 
 2006-01-03  Henning Meier-Geinitz <henning@meier-geinitz.de>
 
diff --git a/PROBLEMS b/PROBLEMS
index 256443e3f..4eef21a19 100644
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -1,4 +1,4 @@
-Last update: 2003-02-09
+Last update: 2006-01-05
 
 - Avoiding damage on flatbed scanners
 
@@ -13,18 +13,6 @@ Last update: 2003-02-09
   safety-guard may not work. Please report errors like this to the author of
   the backend or the sane-devel mailing list.
 
-- pnm backend disabled by default
-
-  If the pnm backend is installed and saned is used to allow users on remote
-  computers to scan on the local machine, pnm files can be read by the remote
-  user. This is limited to the files saned can access (usually it's running as
-  user "sane"). All pnm files can be read if saned runs as root which isn't
-  recommended anyway. The pnm backend is disabled by default. If you want to
-  use it, enable it with configure (see configure --help for details). Be sure
-  that only trusted users can access the pnm backend over saned. As the pnm
-  backend is ususally used for testing, the "test" backend should be used
-  instead.
-
 - Security problems with saned (SANE network scanning daemon)
 
   saned is not intended to be exposed to the internet or other non-trusted