Conversation
Perl is now a CNA, able to assign their own CVE ids, this is great news!
https://security.metacpan.org/2025/02/25/cpansec-is-cna-for-perl-and-cpan.html

Just in time for my talk about this very topic in a few weeks about how all open source projects should be doing this:
https://lfms25.sched.com/event/1urXE/take-control-over-your-projects-cve-entries-before-someone-else-does-greg-kroah-hartman-linux-foundation
3
37
54

@gregkh I spotted perl has MITRE as root, like most.To me it feels like redhat or something would be a better fit...

2
0
0
@bagder As Red Hat just became a root at the same time Perl became a CNA, odds are that wasn't an option yet. But yes, going forward I think having most/many open source groups be under Red Hat is a good option to help reduce the load on MITRE.
1
0
2

@gregkh I want to watch this talk and compare notes as glibc is a CNA, but I've got a conflict all day on the 19th. Will this be recorded? I've only ever seen the keynotes recorded.

0
0
0

@bagder @gregkh when we were applying we defaulted to Mitre. We never really looked at the reasons to choose a different root.

0
0
0

@gregkh awesome if you want to mention this in your talk!

Just for clarity, though – It's the CPAN Security Group (@cpansec) which is now the CNA on behalf of both CPAN and Perl.

This group is different from the security folks in p5p-porters list, the Perl Steering Council, and the Perl Toolchain Gang // Summit folks – though there's some membership overlap. 😃

1
0
0
@sjn @cpansec Thanks for the clarification, and yes, I will mention it!
0
0
1