Searched full:boringssl (Results 1 – 25 of 3215) sorted by relevance
12345678910>>...129
| /external/rust/android-crates-io/crates/quiche/ |
| D | .android-checksum.json | 1 …boringssl/CMakeLists.txt":"bbd180f90a3e139200068cbf171f8a45614d82be961c22a3a5309330eed41b11","deps…
|
| D | .cargo-checksum.json | 1 …boringssl/CMakeLists.txt":"67ec6239d9c1c85b364f703df3d1c9c02d2cf60d9f01e9088a779469b6f412c0","deps…
|
| /external/boringssl/src/infra/config/generated/ |
| D | luci-notify.cfg | 13 recipients: "boringssl@google.com"
19 repository: "https://boringssl.googlesource.com/boringssl"
28 recipients: "boringssl@google.com"
34 repository: "https://boringssl.googlesource.com/boringssl"
43 recipients: "boringssl@google.com"
49 repository: "https://boringssl.googlesource.com/boringssl"
58 recipients: "boringssl@google.com"
64 repository: "https://boringssl.googlesource.com/boringssl"
73 recipients: "boringssl@google.com"
79 repository: "https://boringssl.googlesource.com/boringssl"
[all …]
|
| D | commit-queue.cfg | 17 url: "https://boringssl-review.googlesource.com"
19 name: "boringssl"
25 committer_list: "project-boringssl-committers"
26 dry_run_access_list: "project-boringssl-tryjob-access"
30 name: "boringssl/try/android_aarch64"
34 name: "boringssl/try/android_aarch64_compile"
37 name: "boringssl/try/android_aarch64_fips"
41 name: "boringssl/try/android_aarch64_fips_compile"
44 name: "boringssl/try/android_aarch64_fips_noasm"
48 name: "boringssl/try/android_aarch64_fips_noasm_compile"
[all …]
|
| D | luci-milo.cfg | 9 name: "BoringSSL Main Console"
10 repo_url: "https://boringssl.googlesource.com/boringssl"
14 name: "buildbucket/luci.boringssl.ci/android_aarch64"
19 name: "buildbucket/luci.boringssl.ci/android_aarch64_rel"
24 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips"
29 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_noasm"
34 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_static"
39 name: "buildbucket/luci.boringssl.ci/android_arm"
44 name: "buildbucket/luci.boringssl.ci/android_arm_rel"
49 name: "buildbucket/luci.boringssl.ci/android_arm_fips"
[all …]
|
| D | cr-buildbucket.cfg | 26 ' "group": "client.boringssl"'
33 ' "recipe": "boringssl"'
44 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
63 ' "group": "client.boringssl"'
72 ' "recipe": "boringssl"'
83 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
102 ' "group": "client.boringssl"'
112 ' "recipe": "boringssl"'
123 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
142 ' "group": "client.boringssl"'
[all …]
|
| /external/cronet/stable/third_party/boringssl/src/infra/config/generated/ |
| D | luci-notify.cfg | 13 recipients: "boringssl@google.com"
19 repository: "https://boringssl.googlesource.com/boringssl"
28 recipients: "boringssl@google.com"
34 repository: "https://boringssl.googlesource.com/boringssl"
43 recipients: "boringssl@google.com"
49 repository: "https://boringssl.googlesource.com/boringssl"
58 recipients: "boringssl@google.com"
64 repository: "https://boringssl.googlesource.com/boringssl"
73 recipients: "boringssl@google.com"
79 repository: "https://boringssl.googlesource.com/boringssl"
[all …]
|
| D | commit-queue.cfg | 17 url: "https://boringssl-review.googlesource.com"
19 name: "boringssl"
25 committer_list: "project-boringssl-committers"
26 dry_run_access_list: "project-boringssl-tryjob-access"
30 name: "boringssl/try/android_aarch64"
34 name: "boringssl/try/android_aarch64_compile"
37 name: "boringssl/try/android_aarch64_fips"
41 name: "boringssl/try/android_aarch64_fips_compile"
44 name: "boringssl/try/android_aarch64_fips_noasm"
48 name: "boringssl/try/android_aarch64_fips_noasm_compile"
[all …]
|
| D | luci-milo.cfg | 9 name: "BoringSSL Main Console"
10 repo_url: "https://boringssl.googlesource.com/boringssl"
14 name: "buildbucket/luci.boringssl.ci/android_aarch64"
19 name: "buildbucket/luci.boringssl.ci/android_aarch64_rel"
24 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips"
29 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_noasm"
34 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_static"
39 name: "buildbucket/luci.boringssl.ci/android_arm"
44 name: "buildbucket/luci.boringssl.ci/android_arm_rel"
49 name: "buildbucket/luci.boringssl.ci/android_arm_fips"
[all …]
|
| D | cr-buildbucket.cfg | 26 ' "group": "client.boringssl"'
33 ' "recipe": "boringssl"'
44 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
63 ' "group": "client.boringssl"'
72 ' "recipe": "boringssl"'
83 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
102 ' "group": "client.boringssl"'
112 ' "recipe": "boringssl"'
123 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
142 ' "group": "client.boringssl"'
[all …]
|
| /external/cronet/tot/third_party/boringssl/src/infra/config/generated/ |
| D | luci-notify.cfg | 13 recipients: "boringssl@google.com"
19 repository: "https://boringssl.googlesource.com/boringssl"
28 recipients: "boringssl@google.com"
34 repository: "https://boringssl.googlesource.com/boringssl"
43 recipients: "boringssl@google.com"
49 repository: "https://boringssl.googlesource.com/boringssl"
58 recipients: "boringssl@google.com"
64 repository: "https://boringssl.googlesource.com/boringssl"
73 recipients: "boringssl@google.com"
79 repository: "https://boringssl.googlesource.com/boringssl"
[all …]
|
| D | commit-queue.cfg | 17 url: "https://boringssl-review.googlesource.com"
19 name: "boringssl"
25 committer_list: "project-boringssl-committers"
26 dry_run_access_list: "project-boringssl-tryjob-access"
30 name: "boringssl/try/android_aarch64"
34 name: "boringssl/try/android_aarch64_compile"
37 name: "boringssl/try/android_aarch64_fips"
41 name: "boringssl/try/android_aarch64_fips_compile"
44 name: "boringssl/try/android_aarch64_fips_noasm"
48 name: "boringssl/try/android_aarch64_fips_noasm_compile"
[all …]
|
| D | luci-milo.cfg | 9 name: "BoringSSL Main Console"
10 repo_url: "https://boringssl.googlesource.com/boringssl"
14 name: "buildbucket/luci.boringssl.ci/android_aarch64"
19 name: "buildbucket/luci.boringssl.ci/android_aarch64_rel"
24 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips"
29 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_noasm"
34 name: "buildbucket/luci.boringssl.ci/android_aarch64_fips_static"
39 name: "buildbucket/luci.boringssl.ci/android_arm"
44 name: "buildbucket/luci.boringssl.ci/android_arm_rel"
49 name: "buildbucket/luci.boringssl.ci/android_arm_fips"
[all …]
|
| D | cr-buildbucket.cfg | 26 ' "group": "client.boringssl"'
33 ' "recipe": "boringssl"'
44 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
63 ' "group": "client.boringssl"'
72 ' "recipe": "boringssl"'
83 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
102 ' "group": "client.boringssl"'
112 ' "recipe": "boringssl"'
123 service_account: "boringssl-ci-builder@chops-service-accounts.iam.gserviceaccount.com"
142 ' "group": "client.boringssl"'
[all …]
|
| /external/tink/cc/third_party/boringssl_fips/ |
| D | BUILD.bazel | 4 "boringssl/include/openssl/aead.h",
5 "boringssl/include/openssl/aes.h",
6 "boringssl/include/openssl/arm_arch.h",
7 "boringssl/include/openssl/asn1.h",
8 "boringssl/include/openssl/asn1_mac.h",
9 "boringssl/include/openssl/asn1t.h",
10 "boringssl/include/openssl/base64.h",
11 "boringssl/include/openssl/base.h",
12 "boringssl/include/openssl/bio.h",
13 "boringssl/include/openssl/blowfish.h",
[all …]
|
| /external/armnn/shim/sl/ |
| D | CMakeLists.txt | 36 ${AOSP_MODULES_ROOT}/external/boringssl/src/include
37 ${AOSP_MODULES_ROOT}/external/boringssl/include)
173 ${AOSP_MODULES_ROOT}/external/boringssl/err_data.c
174 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_bitstr.c
175 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_bool.c
176 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_d2i_fp.c
177 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_dup.c
178 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_enum.c
179 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_gentm.c
180 ${AOSP_MODULES_ROOT}/external/boringssl/src/crypto/asn1/a_i2d_fp.c
[all …]
|
| /external/cronet/stable/third_party/boringssl/src/ |
| D | INCORPORATING.md | 1 # Incorporating BoringSSL into a project
4 [main README](./README.md) about the purpose of BoringSSL.
6 If you are porting BoringSSL to a new platform see
7 ["go/boringssl-on-new-platform"](https://goto.corp.google.com/boringssl-on-new-platform) (Google
8 Internal) for information about porting BoringSSL to a new platform for a Google
13 BoringSSL usage typically follows a
15 model. Projects pin to whatever the current latest of BoringSSL is at the time
18 Some systems cannot consume git revisions and expect git tags. BoringSSL tags
21 BoringSSL does not branch at these releases and will not cherry-pick bugfixes to
25 While the BoringSSL repository may contain project-specific branches, e.g.
[all …]
|
| D | SANDBOXING.md | 1 # Using BoringSSL in a Sandbox
3 Sandboxes are a valuable tool for securing applications, so BoringSSL aims to
8 in either BoringSSL or the C library.
10 Some functions in BoringSSL, such as `BIO_new_file`, inherently need OS
30 Callers must assume that any BoringSSL function may perform one of the following
35 Any BoringSSL function may allocate memory via `malloc` and related functions.
39 Any BoringSSL function may call into the platform's thread synchronization
41 These must succeed, or BoringSSL will abort the process. Callers, however, can
42 assume that BoringSSL functions will not spawn internal threads, unless
45 Syscall-filtering sandboxes should note that BoringSSL uses `pthread_rwlock_t`
[all …]
|
| D | PORTING.md | 1 # Porting from OpenSSL to BoringSSL
3 BoringSSL is an OpenSSL derivative and is mostly source-compatible, for the
5 BoringSSL support, provided they do not use removed APIs. In general, see if the
9 BoringSSL's `OPENSSL_VERSION_NUMBER` matches the OpenSSL version it targets.
10 Version checks for OpenSSL should ideally work as-is in BoringSSL. BoringSSL
17 In some cases, BoringSSL-specific code may be necessary. Use the
19 the BoringSSL maintainers about the missing APIs. We will typically add
20 compatibility functions for convenience. In particular, *contact BoringSSL
21 maintainers before working around missing OpenSSL 1.1.0 accessors*. BoringSSL
24 been ported to OpenSSL 1.1.0, so BoringSSL also remains largely compatible with
[all …]
|
| /external/boringssl/src/ |
| D | INCORPORATING.md | 1 # Incorporating BoringSSL into a project
4 [main README](./README.md) about the purpose of BoringSSL.
6 If you are porting BoringSSL to a new platform see
7 ["go/boringssl-on-new-platform"](https://goto.corp.google.com/boringssl-on-new-platform) (Google
8 Internal) for information about porting BoringSSL to a new platform for a Google
13 BoringSSL usage typically follows a
15 model. Projects pin to whatever the current latest of BoringSSL is at the time
18 Some systems cannot consume git revisions and expect git tags. BoringSSL tags
21 BoringSSL does not branch at these releases and will not cherry-pick bugfixes to
25 While the BoringSSL repository may contain project-specific branches, e.g.
[all …]
|
| D | SANDBOXING.md | 1 # Using BoringSSL in a Sandbox
3 Sandboxes are a valuable tool for securing applications, so BoringSSL aims to
8 in either BoringSSL or the C library.
10 Some functions in BoringSSL, such as `BIO_new_file`, inherently need OS
30 Callers must assume that any BoringSSL function may perform one of the following
35 Any BoringSSL function may allocate memory via `malloc` and related functions.
39 Any BoringSSL function may call into the platform's thread synchronization
41 These must succeed, or BoringSSL will abort the process. Callers, however, can
42 assume that BoringSSL functions will not spawn internal threads, unless
45 Syscall-filtering sandboxes should note that BoringSSL uses `pthread_rwlock_t`
[all …]
|
| D | PORTING.md | 1 # Porting from OpenSSL to BoringSSL
3 BoringSSL is an OpenSSL derivative and is mostly source-compatible, for the
5 BoringSSL support, provided they do not use removed APIs. In general, see if the
9 BoringSSL's `OPENSSL_VERSION_NUMBER` matches the OpenSSL version it targets.
10 Version checks for OpenSSL should ideally work as-is in BoringSSL. BoringSSL
17 In some cases, BoringSSL-specific code may be necessary. Use the
19 the BoringSSL maintainers about the missing APIs. We will typically add
20 compatibility functions for convenience. In particular, *contact BoringSSL
21 maintainers before working around missing OpenSSL 1.1.0 accessors*. BoringSSL
24 been ported to OpenSSL 1.1.0, so BoringSSL also remains largely compatible with
[all …]
|
| /external/cronet/tot/third_party/boringssl/src/ |
| D | INCORPORATING.md | 1 # Incorporating BoringSSL into a project
4 [main README](./README.md) about the purpose of BoringSSL.
6 If you are porting BoringSSL to a new platform see
7 ["go/boringssl-on-new-platform"](https://goto.corp.google.com/boringssl-on-new-platform) (Google
8 Internal) for information about porting BoringSSL to a new platform for a Google
13 BoringSSL usage typically follows a
15 model. Projects pin to whatever the current latest of BoringSSL is at the time
18 Some systems cannot consume git revisions and expect git tags. BoringSSL tags
21 BoringSSL does not branch at these releases and will not cherry-pick bugfixes to
25 While the BoringSSL repository may contain project-specific branches, e.g.
[all …]
|
| D | SANDBOXING.md | 1 # Using BoringSSL in a Sandbox
3 Sandboxes are a valuable tool for securing applications, so BoringSSL aims to
8 in either BoringSSL or the C library.
10 Some functions in BoringSSL, such as `BIO_new_file`, inherently need OS
30 Callers must assume that any BoringSSL function may perform one of the following
35 Any BoringSSL function may allocate memory via `malloc` and related functions.
39 Any BoringSSL function may call into the platform's thread synchronization
41 These must succeed, or BoringSSL will abort the process. Callers, however, can
42 assume that BoringSSL functions will not spawn internal threads, unless
45 Syscall-filtering sandboxes should note that BoringSSL uses `pthread_rwlock_t`
[all …]
|
| /external/grpc-grpc/src/python/grpcio/ |
| D | grpc_core_dependencies.py | 1001 'third_party/boringssl-with-bazel/err_data.c',
1002 'third_party/boringssl-with-bazel/src/crypto/asn1/a_bitstr.c',
1003 'third_party/boringssl-with-bazel/src/crypto/asn1/a_bool.c',
1004 'third_party/boringssl-with-bazel/src/crypto/asn1/a_d2i_fp.c',
1005 'third_party/boringssl-with-bazel/src/crypto/asn1/a_dup.c',
1006 'third_party/boringssl-with-bazel/src/crypto/asn1/a_gentm.c',
1007 'third_party/boringssl-with-bazel/src/crypto/asn1/a_i2d_fp.c',
1008 'third_party/boringssl-with-bazel/src/crypto/asn1/a_int.c',
1009 'third_party/boringssl-with-bazel/src/crypto/asn1/a_mbstr.c',
1010 'third_party/boringssl-with-bazel/src/crypto/asn1/a_object.c',
[all …]
|
12345678910>>...129