CentOS 5 still ships with OpenSSL 0.9.8, and is still supported for another year or so. Considering there’s a lot of servers still running CentOS 5 (and possibly older), it feels as if this would have been caught. Especially something as small as a missing semicolon.
Would a linter / compile check to proactively check those things help? — Jacob Perkins Product Owner cPanel Inc. jacob.perk...@cpanel.net <mailto:jacob.perk...@cpanel.net> Office: 713-529-0800 x 4046 Cell: 713-560-8655 > On Dec 21, 2015, at 1:06 PM, Eric Covener <cove...@gmail.com> wrote: > > On Mon, Dec 21, 2015 at 1:48 PM, Jacob Perkins <jacob.perk...@cpanel.net> > wrote: >> This is kind of a show stopper here. I’m surprised something as major as >> code not compiling was not caught before it was sent out. > > This particular failure only occurs when compiling httpd against older > levels of openssl 0.9.8. > It's no surprise to me that none of the handful of people who test new > release candidates test > with contemporary levels of openssl that are actually fit for some use.
signature.asc
Description: Message signed with OpenPGP using GPGMail
