Re:OpenSSL is considering a more aggressive EOL policy
by vertex-four on Thursday June 12, 2014 @01:32PM
(#7884781)
FreeBSD has four releases of their entire operating system in support right now, across three major versions, supported almost entirely by volunteer work. If OpenSSL can't support four minor versions of their security-critical codebase, I don't think it's possible to trust them.
Re:OpenSSL is considering a more aggressive EOL policy
by laumars on Thursday June 12, 2014 @01:46PM
(#7884904)
Yeah true, however I don't think that's a fair comparison. Maintaining older FreeBSD repos wouldn't require large amounts of original code in the same way as maintaining multiple branches of OpenSSL.
Plus the "security-critical" part of your post needs to be emphasised.
Re:OpenSSL is considering a more aggressive EOL policy
by vertex-four on Thursday June 12, 2014 @05:30PM
(#7886074)
> Maintaining older FreeBSD repos wouldn't require large amounts of original code in the same way as maintaining multiple branches of OpenSSL.
Really? FreeBSD repos contain large amounts of both original and external (sometimes modified) code. If there's a security issue, it's entirely possible that all of them need patches.
I do agree that there needs to be some predictability but I also think managing 4 (including betas) code bases add a lot of unnecessary maintenance. If they can remove one branch, enabling them to better focus their time, then I can't see that as a bad thing nor mutually exclusive from having pre-defined EOL dates.