summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDagfinn Ilmari Mannsåker <ilmari@ilmari.org>2020-02-16 17:22:41 +0000
committerDagfinn Ilmari Mannsåker <ilmari@ilmari.org>2020-02-16 17:27:08 +0000
commitef0d5f5f6ff5fd68bc3eae8895729728d5b2579b (patch)
tree27d72d6c911c380e74411bde0222b02d1d131281
parent0b657b1955a40e49c93ca32fe32822f4a8a5205b (diff)
downloadperl-ef0d5f5f6ff5fd68bc3eae8895729728d5b2579b.tar.gz
Storable: linkify alternatives references
Also fix typo Serial → Sereal.
-rw-r--r--dist/Storable/Storable.pm6
-rw-r--r--t/porting/known_pod_issues.dat4
2 files changed, 7 insertions, 3 deletions
diff --git a/dist/Storable/Storable.pm b/dist/Storable/Storable.pm
index f30d1d93a6..164615c79c 100644
--- a/dist/Storable/Storable.pm
+++ b/dist/Storable/Storable.pm
@@ -1227,9 +1227,9 @@ See CVE-2015-1592 and its metasploit module.
If your application requires accepting data from untrusted sources,
you are best off with a less powerful and more-likely safe
serialization format and implementation. If your data is sufficiently
-simple, Cpanel::JSON::XS, Data::MessagePack or Serial are the best
-choices and offers maximum interoperability, but note that Serial is
-unsafe by default.
+simple, L<Cpanel::JSON::XS>, L<Data::MessagePack> or L<Sereal> are the best
+choices and offer maximum interoperability, but note that Sereal is
+L<unsafe by default|Sereal::Decoder/ROBUSTNESS>.
=head1 WARNING
diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat
index 758b4b4940..ad18b675a8 100644
--- a/t/porting/known_pod_issues.dat
+++ b/t/porting/known_pod_issues.dat
@@ -64,6 +64,7 @@ Coro
cpan2dist(1)
CPAN::Changes::Spec
CPAN::Uploader
+Cpanel::JSON::XS
cpanp(1)
CPANPLUS
crypt(3)
@@ -75,6 +76,7 @@ Data::Alias
Data::Dump::Streamer
Data::Entropy
Data::Float
+Data::MessagePack
Data::Structure::Util
Data::Types
Data::Util
@@ -279,6 +281,8 @@ sendmail(1)
sendmsg(2)
sendmsg(3)
sendto(2)
+Sereal
+Sereal::Decoder
setenv(3)
setitimer(2)
setlocale(3)