Justus Winter

> The previous behavior allowed me as a crate author to pre-build bindings and include them with my crate. Our crate, nettle-sys, does not pre-build bindings, and we are also...

> On university systems the users often do not have root access to install the libraries either. That's a red herring. You don't need root to do that. If you...

> Are you proposing to use a separate usebundle=yes option and making useshared=yes the default? Yes. > The patches to the lua source mostly deal with making the code compile...

@satta: The Debian package uses the bundled libraries header files, I'm working on a patch to address this.

While working on that I realized that you don't only embed the libraries, but also build them using your own Makefile and just link them together. I'm somewhat surprised that...

Err, no. Any decent build system allows the creation of statically linked binaries, no need to either bundle libraries nor, if you must do that, side-step the build system of...

Implementing the Rust SOP interface (https://docs.rs/sop) now gives you the CLI frontend for free.

> I'm a bit unclear what to make of the treatment in P-H-C/phc-winner-argon2#173 My take on that is that parameters with associated data (and keyid) have no string representation, but...

I found two documents describing Argon2 in detail: - https://github.com/P-H-C/phc-winner-argon2/blob/master/argon2-specs.pdf Section 3.1, "Inputs" - RFC9106: https://www.rfc-editor.org/rfc/rfc9106.html#name-argon2-inputs-and-outputs Both documents list associated data as inputs to the function. Neither document contains the...

> keyid&data can still be used programmatically Ah, I didn't notice the `ParamsBuilder`. Maybe it would be helpful to link to it from `Params`. I'll update the issue's text.