3 ms·
There used to be the GO FIPS branch: https://github.com/golang/go/tree/dev.boringcrypto/misc/boring https://github.com/golang/go/tree/dev.boringcrypto/misc/bor
by metadat 3y ago
There used to be the GO FIPS branch:
https://github.com/golang/go/tree/dev.boringcrypto/misc/boring https://github.com/golang/go/tree/dev.boringcrypto/misc/bori...
But it looks dead for some time.
However https://github.com/golang-fips/go https://github.com/golang-fips/go sprung up to take it's place.
I wonder why microsoft prefers to maintain it's own in entirety rather than share a piece of the burden.
- abtinf 3y ago> Our goal is to share this implementation with others in the Go community who have the same requirement, and to merge this capability into upstream Go as soon as possible. From the readme.
- gct 3y agoEEE
- metadat 3y agoWhat?
- camkego 3y agoFrom Wikipedia: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... "Embrace, extend, and extinguish" (EEE),[1] also known as "embrace, extend, and exterminate",[2] is a phrase that the U.S. Department of Justice found[3] was used internally by Microsoft[4] to describe its strategy for entering product categories involving widely used open standards, extending those standards with proprietary capabilities, and using the differences to strongly disadvantage its competitors. Please see the Wiki article for the full deal including footnotes.
- cosmotic 3y agoIt's not fair to say EEE in response to every apparently good thing Microsoft does.
- bogantech 3y agoAh yes they're going to extinguish Go with a checks notes... open-source fork