commit | bc4c91ab4655d10b55427ad7d4f1ae21fe2df06b | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue May 18 16:06:30 2021 -0400 |
committer | Adam Langley <agl@google.com> | Thu Jun 03 20:43:22 2021 +0000 |
tree | b780a36261f2aaf6c1629a27ba7d38b51cee2b2f | |
parent | 4848294f43c34268181510a50a747e7b31bc8183 [diff] |
DTLS-SRTP is only defined for DTLS. This avoids needing to worry about the interaction with renegotiation which, in turn, means we can drop the init callback. (If we did support DTLS renegotiation, we'd probably want to forbid the parameter from changing anyway. Changing your SRTP parameters partway through will likely confuse the RTP half of the application anyway.) Change-Id: Ifef1e9479d9df296b69b0d296f6bef57b13da68e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47905 Reviewed-by: Adam Langley <agl@google.com>
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.
Project links:
There are other files in this directory which might be helpful: