2014-06-20 20:00:00 +01:00
|
|
|
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* This package is an SSL implementation written
|
|
|
|
* by Eric Young (eay@cryptsoft.com).
|
|
|
|
* The implementation was written so as to conform with Netscapes SSL.
|
|
|
|
*
|
|
|
|
* This library is free for commercial and non-commercial use as long as
|
|
|
|
* the following conditions are aheared to. The following conditions
|
|
|
|
* apply to all code found in this distribution, be it the RC4, RSA,
|
|
|
|
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
|
|
|
|
* included with this distribution is covered by the same copyright terms
|
|
|
|
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
|
|
|
|
*
|
|
|
|
* Copyright remains Eric Young's, and as such any Copyright notices in
|
|
|
|
* the code are not to be removed.
|
|
|
|
* If this package is used in a product, Eric Young should be given attribution
|
|
|
|
* as the author of the parts of the library used.
|
|
|
|
* This can be in the form of a textual message at program startup or
|
|
|
|
* in documentation (online or textual) provided with the package.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
* "This product includes cryptographic software written by
|
|
|
|
* Eric Young (eay@cryptsoft.com)"
|
|
|
|
* The word 'cryptographic' can be left out if the rouines from the library
|
|
|
|
* being used are not cryptographic related :-).
|
|
|
|
* 4. If you include any Windows specific code (or a derivative thereof) from
|
|
|
|
* the apps directory (application code) you must include an acknowledgement:
|
|
|
|
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*
|
|
|
|
* The licence and distribution terms for any publically available version or
|
|
|
|
* derivative of this code cannot be changed. i.e. this code cannot simply be
|
|
|
|
* copied and put under another distribution licence
|
|
|
|
* [including the GNU Public Licence.]
|
|
|
|
*/
|
|
|
|
/* ====================================================================
|
|
|
|
* Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
*
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
*
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in
|
|
|
|
* the documentation and/or other materials provided with the
|
|
|
|
* distribution.
|
|
|
|
*
|
|
|
|
* 3. All advertising materials mentioning features or use of this
|
|
|
|
* software must display the following acknowledgment:
|
|
|
|
* "This product includes software developed by the OpenSSL Project
|
|
|
|
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
|
|
|
|
*
|
|
|
|
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
|
|
|
|
* endorse or promote products derived from this software without
|
|
|
|
* prior written permission. For written permission, please contact
|
|
|
|
* openssl-core@openssl.org.
|
|
|
|
*
|
|
|
|
* 5. Products derived from this software may not be called "OpenSSL"
|
|
|
|
* nor may "OpenSSL" appear in their names without prior written
|
|
|
|
* permission of the OpenSSL Project.
|
|
|
|
*
|
|
|
|
* 6. Redistributions of any form whatsoever must retain the following
|
|
|
|
* acknowledgment:
|
|
|
|
* "This product includes software developed by the OpenSSL Project
|
|
|
|
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
|
|
|
|
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
|
|
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
|
|
|
|
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
|
|
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
|
|
|
|
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
|
|
|
|
* OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
* ====================================================================
|
|
|
|
*
|
|
|
|
* This product includes cryptographic software written by Eric Young
|
|
|
|
* (eay@cryptsoft.com). This product includes software written by Tim
|
|
|
|
* Hudson (tjh@cryptsoft.com).
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
/*
|
|
|
|
DTLS code by Eric Rescorla <ekr@rtfm.com>
|
|
|
|
|
|
|
|
Copyright (C) 2006, Network Resonance, Inc.
|
|
|
|
Copyright (C) 2011, RTFM, Inc.
|
|
|
|
*/
|
|
|
|
|
2015-09-15 06:48:04 +01:00
|
|
|
#include <openssl/ssl.h>
|
|
|
|
|
2015-04-08 04:05:04 +01:00
|
|
|
#include <string.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2014-06-25 04:27:17 +01:00
|
|
|
#include <openssl/bytestring.h>
|
2014-06-20 20:00:00 +01:00
|
|
|
#include <openssl/err.h>
|
|
|
|
|
2015-04-08 03:38:30 +01:00
|
|
|
#include "internal.h"
|
2014-06-20 20:00:00 +01:00
|
|
|
|
|
|
|
|
Move libssl's internals into the bssl namespace.
This is horrible, but everything else I tried was worse. The goal with
this CL is to take the extern "C" out of ssl/internal.h and move most
symbols to namespace bssl, so we can start using C++ helpers and
destructors without worry.
Complications:
- Public API functions must be extern "C" and match their declaration in
ssl.h, which is unnamespaced. C++ really does not want you to
interleave namespaced and unnamespaced things. One can actually write
a namespaced extern "C" function, but this means, from C++'s
perspective, the function is namespaced. Trying to namespace the
public header would worked but ended up too deep a rabbithole.
- Our STACK_OF macros do not work right in namespaces.
- The typedefs for our exposed but opaque types are visible in the
header files and copied into consuming projects as forward
declarations. We ultimately want to give SSL a destructor, but
clobbering an unnamespaced ssl_st::~ssl_st seems bad manners.
- MSVC complains about ambiguous names if one typedefs SSL to bssl::SSL.
This CL opts for:
- ssl/*.cc must begin with #define BORINGSSL_INTERNAL_CXX_TYPES. This
informs the public headers to create forward declarations which are
compatible with our namespaces.
- For now, C++-defined type FOO ends up at bssl::FOO with a typedef
outside. Later I imagine we'll rename many of them.
- Internal functions get namespace bssl, so we stop worrying about
stomping the tls1_prf symbol. Exported C functions are stuck as they
are. Rather than try anything weird, bite the bullet and reorder files
which have a mix of public and private functions. I expect that over
time, the public functions will become fairly small as we move logic
to more idiomatic C++.
Files without any public C functions can just be written normally.
- To avoid MSVC troubles, some bssl types are renamed to CPlusPlusStyle
in advance of them being made idiomatic C++.
Bug: 132
Change-Id: Ic931895e117c38b14ff8d6e5a273e868796c7581
Reviewed-on: https://boringssl-review.googlesource.com/18124
Reviewed-by: David Benjamin <davidben@google.com>
2017-07-18 21:34:25 +01:00
|
|
|
using namespace bssl;
|
|
|
|
|
2016-05-10 22:19:00 +01:00
|
|
|
static const SRTP_PROTECTION_PROFILE kSRTPProfiles[] = {
|
2014-06-20 20:00:00 +01:00
|
|
|
{
|
2015-07-16 03:06:07 +01:00
|
|
|
"SRTP_AES128_CM_SHA1_80", SRTP_AES128_CM_SHA1_80,
|
2014-06-20 20:00:00 +01:00
|
|
|
},
|
|
|
|
{
|
2015-07-16 03:06:07 +01:00
|
|
|
"SRTP_AES128_CM_SHA1_32", SRTP_AES128_CM_SHA1_32,
|
2014-06-20 20:00:00 +01:00
|
|
|
},
|
2015-12-10 22:29:27 +00:00
|
|
|
{
|
|
|
|
"SRTP_AEAD_AES_128_GCM", SRTP_AEAD_AES_128_GCM,
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"SRTP_AEAD_AES_256_GCM", SRTP_AEAD_AES_256_GCM,
|
|
|
|
},
|
2015-10-30 21:19:01 +00:00
|
|
|
{0, 0},
|
2014-12-16 02:42:07 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
static int find_profile_by_name(const char *profile_name,
|
2015-01-01 20:02:11 +00:00
|
|
|
const SRTP_PROTECTION_PROFILE **pptr,
|
|
|
|
size_t len) {
|
Move libssl's internals into the bssl namespace.
This is horrible, but everything else I tried was worse. The goal with
this CL is to take the extern "C" out of ssl/internal.h and move most
symbols to namespace bssl, so we can start using C++ helpers and
destructors without worry.
Complications:
- Public API functions must be extern "C" and match their declaration in
ssl.h, which is unnamespaced. C++ really does not want you to
interleave namespaced and unnamespaced things. One can actually write
a namespaced extern "C" function, but this means, from C++'s
perspective, the function is namespaced. Trying to namespace the
public header would worked but ended up too deep a rabbithole.
- Our STACK_OF macros do not work right in namespaces.
- The typedefs for our exposed but opaque types are visible in the
header files and copied into consuming projects as forward
declarations. We ultimately want to give SSL a destructor, but
clobbering an unnamespaced ssl_st::~ssl_st seems bad manners.
- MSVC complains about ambiguous names if one typedefs SSL to bssl::SSL.
This CL opts for:
- ssl/*.cc must begin with #define BORINGSSL_INTERNAL_CXX_TYPES. This
informs the public headers to create forward declarations which are
compatible with our namespaces.
- For now, C++-defined type FOO ends up at bssl::FOO with a typedef
outside. Later I imagine we'll rename many of them.
- Internal functions get namespace bssl, so we stop worrying about
stomping the tls1_prf symbol. Exported C functions are stuck as they
are. Rather than try anything weird, bite the bullet and reorder files
which have a mix of public and private functions. I expect that over
time, the public functions will become fairly small as we move logic
to more idiomatic C++.
Files without any public C functions can just be written normally.
- To avoid MSVC troubles, some bssl types are renamed to CPlusPlusStyle
in advance of them being made idiomatic C++.
Bug: 132
Change-Id: Ic931895e117c38b14ff8d6e5a273e868796c7581
Reviewed-on: https://boringssl-review.googlesource.com/18124
Reviewed-by: David Benjamin <davidben@google.com>
2017-07-18 21:34:25 +01:00
|
|
|
const SRTP_PROTECTION_PROFILE *p = kSRTPProfiles;
|
2014-12-16 02:42:07 +00:00
|
|
|
while (p->name) {
|
|
|
|
if (len == strlen(p->name) && !strncmp(p->name, profile_name, len)) {
|
|
|
|
*pptr = p;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
p++;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2014-06-20 20:00:00 +01:00
|
|
|
|
2014-12-16 02:42:07 +00:00
|
|
|
static int ssl_ctx_make_profiles(const char *profiles_string,
|
2015-05-03 20:21:28 +01:00
|
|
|
STACK_OF(SRTP_PROTECTION_PROFILE) **out) {
|
2017-09-21 07:11:35 +01:00
|
|
|
UniquePtr<STACK_OF(SRTP_PROTECTION_PROFILE)> profiles(
|
|
|
|
sk_SRTP_PROTECTION_PROFILE_new_null());
|
|
|
|
if (profiles == nullptr) {
|
2015-06-29 05:28:17 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_SRTP_COULD_NOT_ALLOCATE_PROFILES);
|
2014-12-16 02:42:07 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-09-27 06:28:35 +01:00
|
|
|
const char *col;
|
|
|
|
const char *ptr = profiles_string;
|
2014-12-16 02:42:07 +00:00
|
|
|
do {
|
|
|
|
col = strchr(ptr, ':');
|
2016-09-27 06:28:35 +01:00
|
|
|
|
|
|
|
const SRTP_PROTECTION_PROFILE *profile;
|
|
|
|
if (!find_profile_by_name(ptr, &profile,
|
|
|
|
col ? (size_t)(col - ptr) : strlen(ptr))) {
|
2015-06-29 05:28:17 +01:00
|
|
|
OPENSSL_PUT_ERROR(SSL, SSL_R_SRTP_UNKNOWN_PROTECTION_PROFILE);
|
2017-09-21 07:11:35 +01:00
|
|
|
return 0;
|
2016-09-27 06:28:35 +01:00
|
|
|
}
|
|
|
|
|
2017-09-21 07:11:35 +01:00
|
|
|
if (!sk_SRTP_PROTECTION_PROFILE_push(profiles.get(), profile)) {
|
|
|
|
return 0;
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
if (col) {
|
|
|
|
ptr = col + 1;
|
|
|
|
}
|
|
|
|
} while (col);
|
|
|
|
|
2016-05-09 18:27:01 +01:00
|
|
|
sk_SRTP_PROTECTION_PROFILE_free(*out);
|
2017-09-21 07:11:35 +01:00
|
|
|
*out = profiles.release();
|
2014-12-16 02:42:07 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
int SSL_CTX_set_srtp_profiles(SSL_CTX *ctx, const char *profiles) {
|
|
|
|
return ssl_ctx_make_profiles(profiles, &ctx->srtp_profiles);
|
|
|
|
}
|
|
|
|
|
2015-09-14 06:54:44 +01:00
|
|
|
int SSL_set_srtp_profiles(SSL *ssl, const char *profiles) {
|
2018-05-02 21:11:34 +01:00
|
|
|
return ssl->config != nullptr &&
|
|
|
|
ssl_ctx_make_profiles(profiles, &ssl->config->srtp_profiles);
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
2015-09-14 06:54:44 +01:00
|
|
|
STACK_OF(SRTP_PROTECTION_PROFILE) *SSL_get_srtp_profiles(SSL *ssl) {
|
2018-05-02 21:11:34 +01:00
|
|
|
if (ssl == nullptr) {
|
|
|
|
return nullptr;
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
2018-05-02 21:11:34 +01:00
|
|
|
if (ssl->config == nullptr) {
|
|
|
|
assert(0);
|
|
|
|
return nullptr;
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
2018-05-02 21:11:34 +01:00
|
|
|
return ssl->config->srtp_profiles != nullptr ? ssl->config->srtp_profiles
|
|
|
|
: ssl->ctx->srtp_profiles;
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
2015-09-14 06:54:44 +01:00
|
|
|
const SRTP_PROTECTION_PROFILE *SSL_get_selected_srtp_profile(SSL *ssl) {
|
2018-04-12 21:37:19 +01:00
|
|
|
return ssl->s3->srtp_profile;
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
int SSL_CTX_set_tlsext_use_srtp(SSL_CTX *ctx, const char *profiles) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// This API inverts its return value.
|
2014-12-16 02:42:07 +00:00
|
|
|
return !SSL_CTX_set_srtp_profiles(ctx, profiles);
|
|
|
|
}
|
|
|
|
|
2015-09-14 06:54:44 +01:00
|
|
|
int SSL_set_tlsext_use_srtp(SSL *ssl, const char *profiles) {
|
2017-08-29 21:33:21 +01:00
|
|
|
// This API inverts its return value.
|
2015-09-14 06:54:44 +01:00
|
|
|
return !SSL_set_srtp_profiles(ssl, profiles);
|
2014-12-16 02:42:07 +00:00
|
|
|
}
|