Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 
 
 
 
 
David Benjamin 1269ddd377 Never use the internal session cache for a client. pirms 9 gadiem
crypto Fix comment style in crypto/rand/rand.c. pirms 9 gadiem
decrepit Move arm_arch.h and fix up lots of include paths. pirms 9 gadiem
include/openssl Never use the internal session cache for a client. pirms 9 gadiem
ssl Never use the internal session cache for a client. pirms 9 gadiem
tool Deprecate SSL_library_init. pirms 9 gadiem
util Linkify pipe words. pirms 9 gadiem
.clang-format Inital import. pirms 10 gadiem
.gitignore Fix documentation generation on Windows. pirms 9 gadiem
BUILDING.md Allow ARM capabilities to be set at compile time. pirms 9 gadiem
CMakeLists.txt Silence MSVC warning C4210. pirms 9 gadiem
LICENSE Note that some files carry in Intel license. pirms 9 gadiem
PORTING.md Deprecate SSL_library_init. pirms 9 gadiem
README.md Links in README.md, take two. pirms 9 gadiem
STYLE.md Markdown-ify STYLE. pirms 9 gadiem
codereview.settings Add a codereview.settings file. pirms 10 gadiem

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.