Here's the referenced commit for the interested: <a href="https://github.com/libressl-portable/openbsd/commit/ddd98f8ea741a122952185a36c1396c14c2fda74#diff-027facc0b7c35aa46b0e8fa7b467f1c4" rel="nofollow">https://github.com/libressl-portable/openbsd/commit/ddd98f8e...</a><p>To be honest I'm kinda surprised that even after the 'goto fail' story people still write code in this questionable style(I know this particular issue is not stemming from the lack of curly braces, but still).
The severity of this issue is being overplayed, some programs were returning 1 in callbacks, a lot of software in the wild interpreted it the way LibreSSL did and hence the attempt at error sanitization. There are patches out for OpenBSD 6.1, LibreSSL 2.5.4 contains the fix.<p><a href="https://www.openbsd.org/errata61.html" rel="nofollow">https://www.openbsd.org/errata61.html</a><p><a href="https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.5.4-relnotes.txt" rel="nofollow">https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.5.4-...</a><p>OpenBSD 6.1 users can now also run syspatch(8).