quiche/src/tls.rs and crypto.rs use an unsafe bindings strategy

https://github.com/cloudflare/quiche/blob/master/quiche/src/tls.rs#L1255 contains a pile of hand-written bindings for BoringSSL functions. BoringSSL is not ABI-stable, so this is not a supported way to use the library. This will result in subtle memory errors, with no checking that you've gotten it right.

Indeed, there are already mistakes:
https://github.com/cloudflare/quiche/blob/master/quiche/src/tls.rs#L1442C8-L1443

BoringSSL uses size_t, not int, for those functions. That means this crate only works correctly on calling conventions where int and size_t are compatible. Specifically, on 64-bit platforms, you're relying on the upper half of the 64-bit register having a defined value when it is used to pass in a 32-bit parameter. You're in luck that most calling conventions require this, but this is not guaranteed.

This should be replaced with something robust, e.g. bindgen.

Inspect the hand-written BoringSSL bindings in quiche/src/tls.rs and crypto.rs, including the declarations around tls.rs lines 1255 and 1442. Review how bindgen could replace this strategy and verify that the resulting bindings use the correct BoringSSL types and calling conventions; done means the manual bindings are replaced with a robust approach.