Filippo Valsorda
dd96ded6c8
[dev.boringcrypto.go1.15] all: merge go1.15.15 into dev.boringcrypto.go1.15
|
3 years ago | |
|---|---|---|
| .github | 4 years ago | |
| api | 4 years ago | |
| doc | 3 years ago | |
| lib | 4 years ago | |
| misc | 3 years ago | |
| src | 3 years ago | |
| test | 3 years ago | |
| .gitattributes | 4 years ago | |
| .gitignore | 7 years ago | |
| AUTHORS | 4 years ago | |
| CONTRIBUTING.md | 6 years ago | |
| CONTRIBUTORS | 4 years ago | |
| LICENSE | 8 years ago | |
| PATENTS | 14 years ago | |
| README.boringcrypto.md | 4 years ago | |
| README.md | 6 years ago | |
| SECURITY.md | 5 years ago | |
| favicon.ico | 8 years ago | |
| robots.txt | 13 years ago |
README.boringcrypto.md
dev.boringcrypto branch
We have been working inside Google on a fork of Go that uses BoringCrypto (the core of BoringSSL) for various crypto primitives, in furtherance of some work related to FIPS 140-2. We have heard that some external users of Go would be interested in this code as well, so this branch holds the patches to make Go use BoringCrypto.
Unlike typical dev branches, we do not intend any eventual merge of this code into the master branch. Instead we intend to maintain in this branch the latest release plus BoringCrypto patches.
To be clear, we are not making any statements or representations about the suitability of this code in relation to the FIPS 140-2 standard. Interested users will have to evaluate for themselves whether the code is useful for their own purposes.