BoringSSL?

[gili-labs]

What's your question?

Can I use BoringSSL?

Additional Context

How difficult would it be to use BoringSSL? I am using gRPC as well, which uses BoringSSL. While I could use OpenSSL, it comes at a performance cost.

[Thalhammer]

BoringSSL's Porting Guide states:

BoringSSL is an OpenSSL derivative and is mostly source-compatible, for the subset of OpenSSL retained. Libraries ideally need little to no changes for BoringSSL support, provided they do not use removed APIs. In general, see if the library compiles and, on failure, consult the documentation in the header files and see if problematic features can be removed.

So the OpenSSL code of jwt-cpp should just work with boringSSL as well by providing the correct include paths. Might be worth to try and add official support/CI since I expect the changes to be kinda minimal.