4 ms·
Hilarious build-time dependencies. You need Perl and Go and a C++ toolchain to build a Rust library!
by jeffbee 6y ago
Hilarious build-time dependencies. You need Perl and Go and a C++ toolchain to build a Rust library!
- frenchy 6y agoCan't misuse it if you can't even build it.
- vmchale 6y agoI do admire it!
- makeworld 6y agoNote that these are the requirements of the BoringSSL dependency, not the project itself.
- octoberfranklin 6y agoThat might make BoringSSL a poor fit for use outside of golang. I mean this is kinda like a rust library with a dependency on a Java JVM.
- loeg 6y agoIt's not a runtime dependency.
- brundolf 6y agoIt looks like that's because it's backed by an established SSL library. So this is more of a safely-typed Rust wrapper around that (which means they aren't rolling their own crypto, which is typically considered a good thing)
- jedimastert 6y ago> which means they aren't rolling their own crypto I will point out that BoringSSL is also mainly developed by Google, so...kinda? I still trust it, just a kinda interesting fact
- brundolf 6y agoI think the intended meaning of "your own crypto" is "greenfield crypto"
- baby 6y agoI’d still rather use a pure rust implementation
- kachnuv_ocasek 6y agoOr they could've used a formally verified crypto library such as HACL*.
- deleted 6y ago[deleted]
- pabs3 6y agoTheres a Rust library that uses a Python script to generate part of its Rust code, checks that generated Rust code into git and the crates.io package does not include the Python script, so you can't actually build the crate from source properly.
- ilammy 6y agoTechnically, you can avoid depending on Perl and Go (which are used to generate some assembly code) but you still need C++ toolchain to build most of the BoringSSL. It is still possible to [make Mundane] link against system's OpenSSL. However, that's a bit different set of worms to locate it, auto-generate working FFI bindings, etc.
- sitkack 6y agoCouldn't the assembly code be generated with constexpr?