Lines Matching full:boringssl

1 # How to change BoringSSL's API
3 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…
48 …ommitted atomically with the BoringSSL update. This can only be done for code which only consumes …
56 …constraints, consider adding one to improve compatibility. For example, BoringSSL has many no-op s…
66 …. Depending on the impact, we may fix the consumer, make a small fix to BoringSSL, or revert the c…
68 If we do not ultimately fix the consumer, add a test in BoringSSL to capture the unexpected API con…
78 …asionally do change these behaviors. This is more complex than changing BoringSSL-only behavior du…
80 …BoringSSL with many third-party projects that normally use OpenSSL. Generally, we consider this ou…
82 We lean fairly strongly towards making changes to BoringSSL over patching third-party code, unless …
86 If the patch to support a BoringSSL change can be generally useful to the third-party project, send…
88 …BoringSSL, it is likely problematic to OpenSSL too. Consider filing a bug with them to suggest a c…