kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2,178 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
4119d42e7c
Go to file
David Benjamin 4119d42e7c Tidy up keyblock and CCS logic slightly. 
Move the actual SSL_AEAD_CTX swap into the record layer. Also revise the
intermediate state we store between setup_key_block and
change_cipher_state. With SSL_AEAD_CTX_new abstracted out, keeping the
EVP_AEAD around doesn't make much sense. Just store enough to partition
the key block.

Change-Id: I773fb46a2cb78fa570f00c0a89339c15bbb1d719
Reviewed-on: https://boringssl-review.googlesource.com/6832
Reviewed-by: Adam Langley <alangley@gmail.com>
2016-01-15 20:40:44 +00:00
crypto Rename the curve25519 precomputed tables. 2016-01-15 19:51:05 +00:00
decrepit Fix AES XTS mode key size. 2015-11-19 18:08:33 +00:00
fuzz Update the fuzz tests for the server. 2015-12-22 16:35:07 -08:00
include/openssl Tidy up keyblock and CCS logic slightly. 2016-01-15 20:40:44 +00:00
ssl Tidy up keyblock and CCS logic slightly. 2016-01-15 20:40:44 +00:00
tool Make it possible to tell what curve was used on the server. 2015-12-22 23:12:25 +00:00
util Add curve25519/asm/x25519-asm-x86_64.S. 2016-01-14 22:36:58 +00:00
.clang-format
.gitignore
BUILDING.md Make the instructions for downloading the ARM compiler easier to copy and paste. 2015-10-30 20:47:08 +00:00
CMakeLists.txt Remove NO_ASM define that I accidently included in the previous commit. 2015-12-22 16:34:33 +00:00
codereview.settings
FUZZING.md Update and fix fuzzing instructions. 2015-11-10 23:37:36 +00:00
LICENSE
PORTING.md
README.md Add four, basic fuzz tests. 2015-11-10 19:14:01 +00:00
STYLE.md Update link to Google style guide. 2015-11-03 02:02:12 +00:00

README.md

BoringSSL

BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.

Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.

Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.

BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.

Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.

There are other files in this directory which might be helpful:

  • PORTING.md: how to port OpenSSL-using code to BoringSSL.
  • BUILDING.md: how to build BoringSSL
  • STYLE.md: rules and guidelines for coding style.
  • include/openssl: public headers with API documentation in comments. Also available online.
  • FUZZING.md: information about fuzzing BoringSSL.