-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cryptographically verify manifests #18
Comments
0install style signatures could be a good start. |
I agree. I can't use nix until it's cryptographically secure. |
Mostly irrelevant now that we have signed binary caches (#75). |
Closing, no longer relevant. We don't rely on manifests anymore, and everything uses https now. |
meditans
referenced
this issue
in Ericson2314/nix
Aug 28, 2020
…-check Check IPFS version on startup
3 tasks
3 tasks
zolodev
pushed a commit
to zolodev/nix
that referenced
this issue
Jan 1, 2024
…ents Tutorial: ad hoc developer environments
P-E-Meunier
pushed a commit
to P-E-Meunier/nix
that referenced
this issue
Feb 26, 2025
Fixes issue NixOS#18 This allows for multiple dependencies with different targets. Before this there was an issue with the flate2 crate which had dependencies: [dependencies] [...] miniz_oxide = { version = "0.3.2", optional = true} [target.'cfg(all(target_arch = "wasm32", not(target_os = "emscripten")))'.dependencies] miniz_oxide = "0.3.2" but the generated Cargo.nix would only contain the targeted version: "miniz_oxide" = { packageId = "miniz_oxide 0.3.2 (registry+https://github.com/rust-lang/crates.io-index)"; target = ((target."arch" == "wasm32") && (!(target."os" == "emscripten"))); }; which means that miniz_oxide would not match for non-wasm32 targets, even if it was enabled via a feature. Now the dependency appears twice: { name = "miniz_oxide"; packageId = "miniz_oxide 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)"; optional = true; } { name = "miniz_oxide"; packageId = "miniz_oxide 0.3.3 (registry+https://github.com/rust-lang/crates.io-index)"; target = ((target."arch" == "x86_64")); } so it will match when the target matches or when the feature is enabled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should cryptographically sign channel manifests, and nix-pull should verify them against a set of allowed keys. This way even non-root users could be allowed to do a nix-pull.
The text was updated successfully, but these errors were encountered: