X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlfaq1.pod;h=ad186264e656e3dfd5165bf5d090eb1c822cf003;hb=5d80033ae3014e41bf0e3cd4b86e2265d9f1ba6d;hp=8809495f8ae834641dd0998bb68e44da8aca4668;hpb=cb4d4ad72865eeac1fa808f5648340744ed44a30;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perlfaq1.pod b/pod/perlfaq1.pod
index 8809495..ad18626 100644
--- a/pod/perlfaq1.pod
+++ b/pod/perlfaq1.pod
@@ -259,10 +259,6 @@ http://www.perl.com/CPAN/misc/japh .
 Over a hundred quips by Larry, from postings of his or source code,
 can be found at http://www.perl.com/CPAN/misc/lwall-quotes.txt.gz .
 
-Newer examples can be found by perusing Larry's postings:
-
-    http://x1.dejanews.com/dnquery.xp?QRY=*&DBS=2&ST=PS&defaultOp=AND&LNG=ALL&format=terse&showsort=date&maxhits=100&subjects=&groups=&authors=larry@*wall.org&fromdate=&todate=
-
 =head2 How can I convince my sysadmin/supervisor/employees to use version 5/5.005/Perl instead of some other language?
 
 If your manager or employees are wary of unsupported software, or
@@ -295,8 +291,8 @@ for any given task.  Also mention that the difference between version
 (Well, OK, maybe it's not quite that distinct, but you get the idea.)
 If you want support and a reasonable guarantee that what you're
 developing will continue to work in the future, then you have to run
-the supported version.  As of early March 2001 that probably means
-running either of the releases 5.6.0 (released in March 2000) or
+the supported version.  As of April 2001 that probably means
+running either of the releases 5.6.1 (released in April 2001) or
 5.005_03 (released in March 1999), although 5.004_05 isn't that bad
 if you B<absolutely> need such an old version (released in April 1999)
 for stability reasons.  Anything older than 5.004_05 shouldn't be used.
@@ -310,6 +306,10 @@ In August 2000 in all Linux distributions a new security problem was
 found in the optional 'suidperl' (not built or installed by default)
 in all the Perl branches 5.6, 5.005, and 5.004, see
 http://www.cpan.org/src/5.0/sperl-2000-08-05/
+Perl maintenance releases 5.6.1 and 5.8.0 have this security hole closed.
+Most, if not all, Linux distribution have patches for this
+vulnerability available, see http://www.linuxsecurity.com/advisories/ ,
+but the most recommendable way is to upgrade to at least Perl 5.6.1.
 
 =head1 AUTHOR AND COPYRIGHT