4 ms·
The pre-declared lifetime worry seems unsubstantiated in my opinion. There's no reason why OpenSSL can't have an expected life cycle based around the expected r
by laumars 12y ago
The pre-declared lifetime worry seems unsubstantiated in my opinion. There's no reason why OpenSSL can't have an expected life cycle based around the expected release of the next new version number. eg 1.0.2 might have an ETA of Jan 2015 and 1.0.3 of Jul 2016; so then you know that 1.0.0 will EOL at Jan 2015 and 1.0.1 18 months later.
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.
- vertex-four 12y agoFreeBSD 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.
- laumars 12y agoYeah 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.
- vertex-four 12y ago> 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.