I was also happy enough with the last part, namely installing CPAN modules more securely via cpanm's --verify option, which verifies the integrity of distribution files retrieved from CPAN using CHECKSUMS file and SIGNATURES file (if found in the distribution).
About last year I built perl for a specific project. During installation of packages via CPAN the package I looked into the the signature/verification thing. The effort seemed like a fucking security theater ...
The packages missing the signatures (or using old PAUSE keys) remaining in CPAN the archive undermine the whole process. They ought to be evicted, or updated/replaced with a version with signatures (along with updated PAUSE keys). Have not installed anything from CPAN for myself (but OSen sure do install software on machines that I use😬).
See also ...
Please do tell me (truthfully) that the above is out of date (all the packages have valid signatures & checksums; all use currently active PAUSE keys; packages are downloaded over "https"/secure connection).
In reply to Re: Building Perl and CPAN Modules Securely from Source
by parv
in thread Building Perl and CPAN Modules Securely from Source
by eyepopslikeamosquito
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |