28 ms·
Between openssl-1.0.1k/l and openssl-1.0.1m, a major automated code reformatting was applied. Over 700,000 lines of code appear to have changed. (with whitesp
by a-dub 12y ago
Between openssl-1.0.1k/l and openssl-1.0.1m, a major automated code reformatting was applied. Over 700,000 lines of code appear to have changed. (with whitespace ignored)
They've supplied tags to identify the start and the end of the code reformatting, but it's completely unclear if anyone has verified that they do not result in built binary changes.
https://www.openssl.org/blog/blog/2015/02/11/code-reformat-finished/ https://www.openssl.org/blog/blog/2015/02/11/code-reformat-f...
- iso8859-1 12y agoIf it's possible to do deterministic builds of OpenSSL, it should be pretty easy to verify that, no?
- 0x0 12y agoThat's quite heavy-handed. Funny that the reformatting actually broke the build for some configurations, even going unnoticed for a while(!!!). I'm glad I'm not a downstream maintainer having to deal with all that! :O In fact.. If even a failing build weren't immediately discovered, what are the chances there haven't been introduced other bugs (that wouldn't fail to compile)?