Lines Matching full:boringssl

1 # BoringSSL API Conventions
3 This document describes conventions for BoringSSL APIs. The [style
12 [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's
30 Most functions in BoringSSL may fail, either due to allocation failures or input
38 [err.h](https://commondatastorage.googleapis.com/chromium-boringssl-docs/err.h.html)
50 [improve](https://bugs.chromium.org/p/boringssl/issues/detail?id=38) this
59 BoringSSL allocates memory via `OPENSSL_malloc`, found in `mem.h`. Use
60 `OPENSSL_free`, found in the same header file, to release it. BoringSSL
67 BoringSSL defines a number of structs for use in its APIs. It is a C library,
76 and returned from BoringSSL's APIs. It is an error to instantiate a heap-
109 Other types in BoringSSL are stack-allocated, such as `EVP_MD_CTX`. These
113 Every stack-allocated object in BoringSSL has a *zero state*, analogous to
189 reference. Note a *reference* in BoringSSL refers to an increment (and eventual
194 As BoringSSL's APIs are primarily in C, ownership and lifetime obligations are
197 [API documentation](https://commondatastorage.googleapis.com/chromium-boringssl-docs/headers.html).
214 and Rust, functions in BoringSSL typically only transfer on success.
244 BoringSSL is internally aware of the platform threading library and calls into