Žiadny popis

Katie Hockman 5622128a77 [dev.boringcrypto.go1.13] all: merge go1.13.15 into dev.boringcrypto.go1.13 4 rokov pred
.github 2182bb097d .github: don't render author-facing text in ISSUE_TEMPLATE 5 rokov pred
api 28e8a0c21e [dev.boringcrypto.go1.13] all: merge go1.13 into dev.boringcrypto.go1.13 5 rokov pred
doc 6bf4b23023 [release-branch.go1.13] doc: add CherryPickApproved filter to Release History links 4 rokov pred
lib adcb2b1e7a lib/time: update tz data to 2019b 5 rokov pred
misc bb8a1014a3 [dev.boringcrypto.go1.13] all: merge go1.13.9 into dev.boringcrypto.go1.13 4 rokov pred
src 5622128a77 [dev.boringcrypto.go1.13] all: merge go1.13.15 into dev.boringcrypto.go1.13 4 rokov pred
test 3c1722cf30 [release-branch.go1.13] reflect: zero stack slots before writing to them with write barriers 4 rokov pred
.gitattributes b7a2b1e980 .gitattributes: prevent all magic line ending changes 9 rokov pred
.gitignore ca0f303f2b .gitignore: ignore src/cmd/dist/dist 7 rokov pred
AUTHORS 3d63166232 A: Add Maya Rashish (individual CLA) 5 rokov pred
CONTRIBUTING.md 4c4ce3dc79 all: restore changes from faulty merge/revert 6 rokov pred
CONTRIBUTORS 450a918b6f [release-branch.go1.13] CONTRIBUTORS: second round of updates for Go 1.13 5 rokov pred
LICENSE d0c1888739 doc: revert copyright date to 2009 8 rokov pred
PATENTS 4468e5b376 LICENSE: separate, change PATENTS text 14 rokov pred
README.boringcrypto.md dcdcc38440 [dev.boringcrypto] add README.boringcrypto.md, update VERSION 7 rokov pred
README.md 235c5cf153 README: linkify some paths 6 rokov pred
SECURITY.md b84e0bc61a SECURITY.md: add security file 5 rokov pred
favicon.ico ef694a0110 website: recreate 16px and 32px favicon 8 rokov pred
robots.txt 06a923ada0 godoc: serve robots.txt raw 13 rokov pred

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.