From dcdcc3844046af0182cd3a94c7bb78c99908020e Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Mon, 14 Aug 2017 11:44:27 -0400 Subject: [PATCH] [dev.boringcrypto] add README.boringcrypto.md, update VERSION Change-Id: I415fcc23b62666d78aed3ddc7d2731127c810be3 Reviewed-on: https://go-review.googlesource.com/55471 Run-TryBot: Russ Cox Reviewed-by: Adam Langley --- README.boringcrypto.md | 18 ++++++++++++++++++ VERSION | 1 - 2 files changed, 18 insertions(+), 1 deletion(-) create mode 100644 README.boringcrypto.md delete mode 100644 VERSION diff --git a/README.boringcrypto.md b/README.boringcrypto.md new file mode 100644 index 0000000000..b6f5805429 --- /dev/null +++ b/README.boringcrypto.md @@ -0,0 +1,18 @@ +# dev.boringcrypto branch + +We have been working inside Google on a fork of Go that uses +BoringCrypto (the core of [BoringSSL](https://boringssl.googlesource.com/boringssl/)) for various crypto primitives, in +furtherance of some [work related to FIPS 140-2](http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp2964.pdf). 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. diff --git a/VERSION b/VERSION deleted file mode 100644 index 0a14d06d2c..0000000000 --- a/VERSION +++ /dev/null @@ -1 +0,0 @@ -go1.9rc2 \ No newline at end of file -- 2.48.1