Yeah, that's the quickest fix for some softwares but OpenBSD devs can be really 'uncompromising' when they consider some features broken/dangerous. That's how they managed to have "2 remote holes in default install" for decades I guess :/
Actually, libressl is practical drop-in replacement of openssl if you use only sane parts of openssl's functionality.
Biggest problem now is some upstream softwares still depends on insanity Openbsd devs nuked away, like RAND_egd() or won't admit that libressl actually exist :)
And I guess this is cool thing about libressl: even if it fails to replace openssl for real good, it is still forcing others to advance toward right direction (remember the linux fork fuss last year? You can disagree with me but I myself consider it linux's 'fault' not to have consistent mechanism of extracting entropy....it doesn't have to be arc4random but it could have been better in the first place if this IMO)
Just out of curiosity, what's GPL advocates and FSF's attitude toward APIs and implementation? Since vmkernel uses glibc, it has to implement all the Linux system calls right?
Were there any claims for GPLed programs' APIs before?
This is all cluster*uck of wild guessworks unless they elaborate more on VMware's response or VMware makes formal statements on their position. What a waste of time
Please correct me or feed me link if I'm wrong, but I can't just donate/support this case if they don't elaborate more on VMware side's story. What has exactly happened? LWN's article sounds somewhat, well, 'unbalanced'.
I want real statistics...anyone with interesting source?