libressl guys are very creative about commit comments
libressl guys are very creative about commit comments
Posted Apr 22, 2014 23:53 UTC (Tue) by gb (subscriber, #58328)Parent article: OpenSSL code beyond repair, claims creator of “LibreSSL” fork (Ars Technica)
http://freshbsd.org/search?project=openbsd&q=file.nam...
I decided to share this link after this comment:
Remove support for big-endian i386 and amd64.
Before someone suggests the OpenSSL people are junkies, here is what they mention about this:
/* Most will argue that x86_64 is always little-endian. Well,
* yes, but then we have stratus.com who has modified gcc to
* "emulate" big-endian on x86. Is there evidence that they
* [or somebody else] won't do same for x86_64? Naturally no.
* And this line is waiting ready for that brave soul:-) */
So, yes, they are on drugs. But they are not alone, the stratus.com people are, too.
Posted Apr 23, 2014 1:58 UTC (Wed)
by cesarb (subscriber, #6266)
[Link] (1 responses)
I would love to see a git mirror of their CVS tree, just to be able to follow their commits directly.
Posted Apr 23, 2014 20:35 UTC (Wed)
by Karellen (subscriber, #67644)
[Link]
http://anoncvs.estpak.ee/cgi-bin/cgit/openbsd-src/log/lib...
Posted Apr 23, 2014 2:16 UTC (Wed)
by gfa (guest, #53331)
[Link]
OpenSSL is the most widely used ssl library it's licence is ok to be included in proprietary platforms, i don't see the problem there. most of those systems are behind a firewall (or even more firewalls)
The problem is for the people who run OpenSSL on modern Unices (linux, *BSD) facing internet. this the the group which will be benefited by the fork. We (i'm part of this group) need a 'simple' fast and modern ssl library
libressl guys are very creative about commit comments
libressl guys are very creative about commit comments
libressl guys are very creative about commit comments