Searched full:boringssl (Results 1 – 25 of 508) sorted by relevance
12345678910>>...21
377 "src\\boringssl\\err_data.c " +378 "third_party\\boringssl\\crypto\\asn1\\a_bitstr.c " +379 "third_party\\boringssl\\crypto\\asn1\\a_bool.c " +380 "third_party\\boringssl\\crypto\\asn1\\a_d2i_fp.c " +381 "third_party\\boringssl\\crypto\\asn1\\a_dup.c " +382 "third_party\\boringssl\\crypto\\asn1\\a_enum.c " +383 "third_party\\boringssl\\crypto\\asn1\\a_gentm.c " +384 "third_party\\boringssl\\crypto\\asn1\\a_i2d_fp.c " +385 "third_party\\boringssl\\crypto\\asn1\\a_int.c " +386 "third_party\\boringssl\\crypto\\asn1\\a_mbstr.c " +[all …]
10 PHP_ADD_INCLUDE(PHP_EXT_SRCDIR()/third_party/boringssl/include)402 src/boringssl/err_data.c \403 third_party/boringssl/crypto/asn1/a_bitstr.c \404 third_party/boringssl/crypto/asn1/a_bool.c \405 third_party/boringssl/crypto/asn1/a_d2i_fp.c \406 third_party/boringssl/crypto/asn1/a_dup.c \407 third_party/boringssl/crypto/asn1/a_enum.c \408 third_party/boringssl/crypto/asn1/a_gentm.c \409 third_party/boringssl/crypto/asn1/a_i2d_fp.c \410 third_party/boringssl/crypto/asn1/a_int.c \[all …]
771 s.files += %w( third_party/boringssl/crypto/asn1/asn1_locl.h )772 s.files += %w( third_party/boringssl/crypto/bio/internal.h )773 s.files += %w( third_party/boringssl/crypto/bytestring/internal.h )774 s.files += %w( third_party/boringssl/crypto/cipher_extra/internal.h )775 s.files += %w( third_party/boringssl/crypto/conf/conf_def.h )776 s.files += %w( third_party/boringssl/crypto/conf/internal.h )777 s.files += %w( third_party/boringssl/crypto/err/internal.h )778 s.files += %w( third_party/boringssl/crypto/evp/internal.h )779 s.files += %w( third_party/boringssl/crypto/fipsmodule/aes/aes.c )780 s.files += %w( third_party/boringssl/crypto/fipsmodule/aes/internal.h )[all …]
1761 'target_name': 'boringssl',1766 'src/boringssl/err_data.c',1767 'third_party/boringssl/crypto/asn1/a_bitstr.c',1768 'third_party/boringssl/crypto/asn1/a_bool.c',1769 'third_party/boringssl/crypto/asn1/a_d2i_fp.c',1770 'third_party/boringssl/crypto/asn1/a_dup.c',1771 'third_party/boringssl/crypto/asn1/a_enum.c',1772 'third_party/boringssl/crypto/asn1/a_gentm.c',1773 'third_party/boringssl/crypto/asn1/a_i2d_fp.c',1774 'third_party/boringssl/crypto/asn1/a_int.c',[all …]
776 <file baseinstalldir="/" name="third_party/boringssl/crypto/asn1/asn1_locl.h" role="src" />777 <file baseinstalldir="/" name="third_party/boringssl/crypto/bio/internal.h" role="src" />778 <file baseinstalldir="/" name="third_party/boringssl/crypto/bytestring/internal.h" role="src" />779 … <file baseinstalldir="/" name="third_party/boringssl/crypto/cipher_extra/internal.h" role="src" />780 <file baseinstalldir="/" name="third_party/boringssl/crypto/conf/conf_def.h" role="src" />781 <file baseinstalldir="/" name="third_party/boringssl/crypto/conf/internal.h" role="src" />782 <file baseinstalldir="/" name="third_party/boringssl/crypto/err/internal.h" role="src" />783 <file baseinstalldir="/" name="third_party/boringssl/crypto/evp/internal.h" role="src" />784 <file baseinstalldir="/" name="third_party/boringssl/crypto/fipsmodule/aes/aes.c" role="src" />785 …<file baseinstalldir="/" name="third_party/boringssl/crypto/fipsmodule/aes/internal.h" role="src" …[all …]
376 'src/boringssl/err_data.c',377 'third_party/boringssl/crypto/asn1/a_bitstr.c',378 'third_party/boringssl/crypto/asn1/a_bool.c',379 'third_party/boringssl/crypto/asn1/a_d2i_fp.c',380 'third_party/boringssl/crypto/asn1/a_dup.c',381 'third_party/boringssl/crypto/asn1/a_enum.c',382 'third_party/boringssl/crypto/asn1/a_gentm.c',383 'third_party/boringssl/crypto/asn1/a_i2d_fp.c',384 'third_party/boringssl/crypto/asn1/a_int.c',385 'third_party/boringssl/crypto/asn1/a_mbstr.c',[all …]
25 'boringssl/util/bot/android_ndk': {30 'boringssl/util/bot/android_tools': {35 'boringssl/util/bot/gyp':38 'boringssl/util/bot/libFuzzer': {45 'boringssl/util/bot/libcxx': {49 'boringssl/util/bot/libcxxabi': {57 'boringssl/util/bot/android_tools',70 '-s', 'boringssl/util/bot/cmake-linux64.tar.gz.sha1',78 'boringssl/util/bot/extract.py',79 'boringssl/util/bot/cmake-linux64.tar.gz',[all …]
1 # Incorporating BoringSSL into a project4 [main README](/README.md) about the purpose of BoringSSL.9 BoringSSL as an external repository by using a commit from the16 name = "boringssl",18 remote = "https://boringssl.googlesource.com/boringssl",26 Typically projects create a `third_party/boringssl` directory to put27 BoringSSL-specific files into. The source code of BoringSSL itself goes into28 `third_party/boringssl/src`, either by copying or as a31 It's generally a mistake to put BoringSSL's source code into32 `third_party/boringssl` directly because pre-built files and custom build files[all …]
1 # Porting from OpenSSL to BoringSSL3 BoringSSL is an OpenSSL derivative and is mostly source-compatible, for the5 BoringSSL support, provided they do not use removed APIs. In general, see if the9 BoringSSL's `OPENSSL_VERSION_NUMBER` matches the OpenSSL version it targets.10 Version checks for OpenSSL should ideally work as-is in BoringSSL. BoringSSL17 In some cases, BoringSSL-specific code may be necessary. Use the19 the BoringSSL maintainers about the missing APIs. We will typically add20 compatibility functions for convenience. In particular, *contact BoringSSL21 maintainers before working around missing OpenSSL 1.1.0 accessors*. BoringSSL24 been ported to OpenSSL 1.1.0, so BoringSSL also remains largely compatible with[all …]
1 # How to change BoringSSL's API3 BoringSSL has more flexibility in changing things than many other library projects because we have …13 …ial measures. Any problems can be handled when the affected consumer updates BoringSSL and notices.19 …BoringSSL consumers are conveniently indexed in various Code Search instances. This can predict th…23 …gh cost (from having to fix consumers) and relatively little benefit to BoringSSL, it may not be w…25 Conversely, a change that leads to a major improvement to all BoringSSL consumers, at the cost of f…39 …BoringSSL's `master` branch directly. It is pushed into Android, where it consumes Android's `exte…44 …ON < N` preprocessor logic. Leave a comment to remove this later, linking to your BoringSSL change.45 …` check has propagated to relevant copies of the consuming repository, submit the BoringSSL change.46 4. When the BoringSSL change has propagated to relevant copies of BoringSSL, remove the staging log…[all …]
1 # BoringSSL chapter3 BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.5 Although BoringSSL is an open source project, it is not intended for general10 Programs ship their own copies of BoringSSL when they use it and we update15 BoringSSL arose because Google used OpenSSL for many years in various ways and,21 Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's26 * [PORTING.md](/PORTING.md): how to port OpenSSL-using code to BoringSSL.27 * [BUILDING.md](/BUILDING.md): how to build BoringSSL28 * [INCORPORATING.md](/INCORPORATING.md): how to incorporate BoringSSL into a project.29 …* [API-CONVENTIONS.md](/API-CONVENTIONS.md): general API conventions for BoringSSL consumers and d…[all …]
1 # BoringSSL API Conventions3 This document describes conventions for BoringSSL APIs. The [style12 [online](https://commondatastorage.googleapis.com/chromium-boringssl-docs/headers.html).22 Do not write `typedef struct foo_st FOO` or try otherwise to define BoringSSL's30 Most functions in BoringSSL may fail, either due to allocation failures or input38 [err.h](https://commondatastorage.googleapis.com/chromium-boringssl-docs/err.h.html)50 [improve](https://bugs.chromium.org/p/boringssl/issues/detail?id=38) this59 BoringSSL allocates memory via `OPENSSL_malloc`, found in `mem.h`. Use60 `OPENSSL_free`, found in the same header file, to release it. BoringSSL67 BoringSSL defines a number of structs for use in its APIs. It is a C library,[all …]
1 # Building BoringSSL6 BoringSSL into another project with a pre-existing build system, see80 the BoringSSL headers.91 It's possible to build BoringSSL with the Android NDK using CMake. Recent135 BoringSSL's build system has experimental support for adding a custom prefix to136 all symbols. This can be useful when linking multiple versions of BoringSSL in157 BoringSSL maintainers if making use of it.171 currently cannot be used to build BoringSSL.179 By default, on Linux-based systems, BoringSSL will try to use `getauxval` and197 run-time, BoringSSL will likely crash.[all …]
25 '../../third_party/boringssl'))36 return 'third_party/boringssl/' + filename[4:]38 return 'src/boringssl/' + filename42 return 'third_party/boringssl/' + arg60 'name': 'boringssl',71 # See https://boringssl-review.googlesource.com/c/boringssl/+/1694674 'boringssl': True,75 'defaults': 'boringssl',82 'boringssl': True,83 'defaults': 'boringssl',[all …]
17 # Check if the commit version of BoringSSL podspec, BoringSSL submodule, and18 # the shadowed symbol list are all based on the same BoringSSL commit.23 boringssl_podspec_original="../../src/objective-c/BoringSSL-GRPC.podspec"26 # Check BoringSSL version matches27 ver1=$(git submodule |grep "boringssl " | awk '{print $1}' | head -n 1)30 …BoringSSL podspec (src/objective-c/BoringSSL.podspec), BoringSSL submodule (third_party/boringssl)…
16 # Generate the list of boringssl symbols that need to be shadowed based on the17 # current boringssl submodule. Requires local toolchain to build boringssl.24 ssl_lib='../../third_party/boringssl/build/ssl/libssl.a'25 crypto_lib='../../third_party/boringssl/build/crypto/libcrypto.a'27 # Generate boringssl archives28 ( cd ../../third_party/boringssl ; mkdir -p build ; cd build ; cmake .. ; make )34 …grep -v ' bssl::' | # Filter BoringSSL symbols since they are already namespa…39 commit=$(git submodule | grep "boringssl " | awk '{print $1}' | head -n 1)
17 set(boringssl_INCLUDE_DIR ${CMAKE_CURRENT_BINARY_DIR}/boringssl/src/boringssl/include)18 #set(boringssl_EXTRA_INCLUDE_DIR ${CMAKE_CURRENT_BINARY_DIR}/boringssl/src)19 set(boringssl_URL https://boringssl.googlesource.com/boringssl)21 set(boringssl_BUILD ${CMAKE_BINARY_DIR}/boringssl/src/boringssl-build)34 ExternalProject_Add(boringssl35 PREFIX boringssl
5071 "boringssl", 5085 "boringssl", 5099 "boringssl", 5113 "boringssl", 5127 "boringssl", 5141 "boringssl", 5155 "boringssl", 5169 "boringssl", 5183 "boringssl", 5197 "boringssl", [all …]
32 #### BoringSSL subsubsection33 Before you can build BoringSSL, you'll first need to set up its34 [prerequisites](https://boringssl.googlesource.com/boringssl/+/HEAD/BUILDING.md#Build-Prerequisites…39 Checkout BoringSSL to a directory of your choice and then build as follows:42 git clone https://boringssl.googlesource.com/boringssl43 cd boringssl
16 #include "third_party/boringssl/src/include/openssl/evp.h"17 #include "third_party/boringssl/src/include/openssl/rand.h"32 // algorithms available in NSS but not BoringSSL and vice in GenerateRandomKey()33 // versa. Note that BoringSSL does not support AES-192. in GenerateRandomKey()63 // algorithms available in NSS but not BoringSSL and vice in DeriveKeyFromPassword()64 // versa. Note that BoringSSL does not support AES-192. in DeriveKeyFromPassword()92 // algorithms available in NSS but not BoringSSL and vice in Import()93 // versa. Note that BoringSSL does not support AES-192. in Import()
7 git clone https://boringssl.googlesource.com/boringssl src22 git commit -m "external/boringssl: Sync to ${new_revision}.26 https://boringssl.googlesource.com/boringssl/+log/${old_revision}..${new_revision}
1 name: "boringssl"2 description: "BoringSSL is a fork of OpenSSL that is designed to meet Google's needs."6 value: "https://boringssl.googlesource.com/boringssl"
1 # Chrome asumes boringssl, while system installed ssl library may not.23 -#include "third_party/boringssl/src/include/openssl/crypto.h"24 -#include "third_party/boringssl/src/include/openssl/err.h"55 -#include "third_party/boringssl/src/include/openssl/base.h"77 -#include "third_party/boringssl/src/include/openssl/mem.h"78 -#include "third_party/boringssl/src/include/openssl/sha.h"
3 REM selected the BoringSSL revision. Must be run from the top-level11 echo Usage: %0 ^<boringssl revision^> ^<repository ID^>15 REM TODO(flooey): The BoringSSL directory needs to be at ../boringssl16 pushd ..\boringssl
46 // CRYPTO_is_confidential_build returns one if the linked version of BoringSSL50 // internal version of BoringSSL.53 // CRYPTO_has_asm returns one unless BoringSSL was built with OPENSSL_NO_ASM,57 // FIPS_mode returns zero unless BoringSSL is built with BORINGSSL_FIPS, in70 #define OPENSSL_VERSION_TEXT "OpenSSL 1.1.0 (compatible; BoringSSL)"79 // "BoringSSL" if |which| is |OPENSSL_VERSION| and placeholder strings131 // FIPS_mode_set returns one if |on| matches whether BoringSSL was built with