picosnitch
1.0.3Eval errorMonitor network traffic per executable with hashing
Planning log · · This campaign
pkgs/by-name/pi/picosnitch/package.nixPackage ‘picosnitch-1.0.3’ is marked as insecure, refusing to evaluate.
Full diagnostic
GC Warning: Failed to expand heap by 4194304 KiB
error:
… while evaluating attribute 'drv'
at /nix/store/lxf05zrla99j7c7z65cr7ix19hyq4irv-filnix-experiment-0.10.1/lib/experiment/planner.nix:14:3:
13| {
14| drv = p.drvPath;
| ^
15| name = p.name;
… while evaluating the attribute 'drvPath'
at /nix/store/nxpf5r8aci7fcrvmwh50m294cq38w3v2-source/lib/customisation.nix:418:7:
417| // {
418| drvPath =
| ^
419| assert condition;
(stack trace truncated; use '--show-trace' to show the full, detailed trace)
error: Package ‘picosnitch-1.0.3’ in /nix/store/nxpf5r8aci7fcrvmwh50m294cq38w3v2-source/pkgs/by-name/pi/picosnitch/package.nix:36 is marked as insecure, refusing to evaluate.
Known issues:
- Allows an unprivileged user to write to arbitrary files as root; see https://github.com/elesiuta/picosnitch/issues/40
You can install it anyway by allowing this package, using the
following methods:
a) To temporarily allow all insecure packages, you can use an environment
variable for a single invocation of the nix tools:
$ export NIXPKGS_ALLOW_INSECURE=1
Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
then pass `--impure` in order to allow use of environment variables.
b) for `nixos-rebuild` you can add ‘picosnitch-1.0.3’ to
`nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
like so:
{
nixpkgs.config.permittedInsecurePackages = [
"picosnitch-1.0.3"
];
}
c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
‘picosnitch-1.0.3’ to `permittedInsecurePackages` in
~/.config/nixpkgs/config.nix, like so:
{
permittedInsecurePackages = [
"picosnitch-1.0.3"
];
}
Direct dependencies
None recorded.
Selected dependents
None recorded.