Home Explore Help
Sign In
mirror
/
go
mirror of https://github.com/golang/go
1
0
Fork 0
Files Issues 0 Wiki

No Description

Branch: dev.boringcrypto.go1.12
Branches Tags
go
ZIP TAR.GZ
Filippo Valsorda 9e5b1367cb [dev.boringcrypto.go1.12] all: merge go1.12.17 into dev.boringcrypto.go1.12 4 years ago
.github 2182bb097d .github: don't render author-facing text in ISSUE_TEMPLATE 6 years ago
api 4ed8ad4d69 [dev.boringcrypto] all: merge master into dev.boringcrypto 5 years ago
doc b293f01b4a [release-branch.go1.12] doc: document Go 1.12.17 4 years ago
lib af3c480967 lib/time: update tzdata to 2018i 5 years ago
misc f74e68136c [dev.boringcrypto.go1.12] all: merge go1.12.16 into dev.boringcrypto.go1.12 4 years ago
src 9e5b1367cb [dev.boringcrypto.go1.12] all: merge go1.12.17 into dev.boringcrypto.go1.12 4 years ago
test 4e15604ada [release-branch.go1.12] cmd/link: increase the function call limit in stkcheck 5 years ago
.gitattributes b7a2b1e980 .gitattributes: prevent all magic line ending changes 10 years ago
.gitignore ca0f303f2b .gitignore: ignore src/cmd/dist/dist 7 years ago
AUTHORS cd06b2d00d A+C: change email address for Elias Naur 5 years ago
CONTRIBUTING.md 4c4ce3dc79 all: restore changes from faulty merge/revert 6 years ago
CONTRIBUTORS 737695231d CONTRIBUTORS: second round of updates for Go 1.12 5 years ago
LICENSE d0c1888739 doc: revert copyright date to 2009 8 years ago
PATENTS 4468e5b376 LICENSE: separate, change PATENTS text 14 years ago
README.boringcrypto.md dcdcc38440 [dev.boringcrypto] add README.boringcrypto.md, update VERSION 7 years ago
README.md 235c5cf153 README: linkify some paths 6 years ago
favicon.ico ef694a0110 website: recreate 16px and 32px favicon 8 years ago
robots.txt 06a923ada0 godoc: serve robots.txt raw 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 I intend to create a new branch dev.boringcrypto that will hold 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 that branch the latest release plus BoringCrypto patches. In this sense it is a bit like dev.typealias holding go1.8+type alias 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.