3 ms·
> wrap an existing C crypto library I know it's mostly semantics but calling C from C++ still requires some wrapping(extern "C", integrating build system, etc)
by vvanders 9y ago
> wrap an existing C crypto library
I know it's mostly semantics but calling C from C++ still requires some wrapping(extern "C", integrating build system, etc).
I've found with bindgen unless there's some crazy macro shenanigans going on it's actually quicker for me to integrate C libraries into Rust then wrangling CMake/Make/etc. The C FFI is very much a first-class citizen in Rust.
Even doubly so if we're talking about a cross-platform library.
- lambdafu 9y agoNeoPG uses Botan, which is a crypto library written in C++. I recommend reading its source code and comparing it with, for example, libgcrypt.
- adultSwim 9y agoIs most of the removed code functionality that is now in the crypto library used, Botan? A blog post on the decision to use an external library might be good. Is there a reason to think that the library will be better maintained than code with similar functionality in GPG? Great work by the way! Thank you!