tree: 1426ea572717a3c280cf4ddec7451044f61703cb [path history] [tgz]
  1. bbig/
  2. bcache/
  3. fipstls/
  4. sig/
  5. syso/
  6. aes.go
  7. boring.go
  8. boring_test.go
  12. div_test.c
  13. doc.go
  14. Dockerfile
  15. ecdh.go
  16. ecdsa.go
  17. goboringcrypto.h
  18. hmac.go
  20. notboring.go
  21. rand.go
  23. rsa.go
  24. sha.go

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. We have heard that some external users of Go would be interested in this code as well, so we have published this code here in the main Go repository behind the setting GOEXPERIMENT=boringcrypto.

Use of GOEXPERIMENT=boringcrypto outside Google is unsupported. This mode is not part of the Go 1 compatibility rules, and it may change incompatibly or break in other ways at any time.

To be clear, we are not making any statements or representations about the suitability of this code in relation to the FIPS 140 standard. Interested users will have to evaluate for themselves whether the code is useful for their own purposes.

This directory holds the core of the BoringCrypto implementation as well as the build scripts for the module itself: syso/*.syso.

syso/goboringcrypto_linux_amd64.syso is built with:

GOARCH=amd64 ./

syso/goboringcrypto_linux_arm64.syso is built with:

GOARCH=arm64 ./

Both run on an x86 Debian Linux system using Docker. For the arm64 build to run on an x86 system, you need

apt-get install qemu-user-static qemu-binfmt-support

to allow the x86 kernel to run arm64 binaries via QEMU.

See for more details about the build.