4 commits

Author	SHA1	Message	Date
John Ericson	f3e1c47f47	Separate headers from source files ... The short answer for why we need to do this is so we can consistently do `#include "nix/..."`. Without this change, there are ways to still make that work, but they are hacky, and they have downsides such as making it harder to make sure headers from the wrong Nix library (e..g. `libnixexpr` headers in `libnixutil`) aren't being used. The C API alraedy used `nix_api_*`, so its headers are *not* put in subdirectories accordingly. Progress on #7876 We resisted doing this for a while because it would be annoying to not have the header source file pairs close by / easy to change file path/name from one to the other. But I am ameliorating that with symlinks in the next commit.	2025-03-31 12:20:25 -04:00
John Ericson	2b6b03d8df	Ensure error messages don't leak private key ... Since #8766, invalid base64 is rendered in errors, but we don't actually want to show this in the case of an invalid private keys. Co-Authored-By: Eelco Dolstra <edolstra@gmail.com>	2024-09-23 16:36:48 -04:00
Alyssa Ross	9cc550d652	Don't refer to public keys as secret keys in error ... This constructor is used for public keys as well.	2024-08-31 16:00:11 +02:00
John Ericson	12bb8cdd38	Signer infrastructure: Prep for #9076 ... This sets up infrastructure in libutil to allow for signing other than by a secret key in memory. #9076 uses this to implement remote signing. (Split from that PR to allow reviewing in smaller chunks.) Co-Authored-By: Raito Bezarius <masterancpp@gmail.com>	2024-01-03 16:13:55 -05:00

Renamed from src/libstore/crypto.cc (Browse further)