nixbot

builds

failed eval checks.aarch64-linux.nixos-the-doctor build #7 · raw · eval 3.8 s · 365.3 MiB allocated · ·

1error:2       … while evaluating a branch condition3         at «string»:25:5:4           24|     v:5           25|     if !builtins.isAttrs v || isDrv v then6             |     ^7           26|       v89       … in the left operand of the OR (||) operator10         at «string»:25:28:11           24|     v:12           25|     if !builtins.isAttrs v || isDrv v then13             |                            ^14           26|       v1516       … while evaluating definitions from `/nix/store/9iv83r72z5xwgylkwms1qip1ijnr6jqs-source/modules/transposition.nix':1718       … while evaluating definitions from `/nix/store/pvxwgpmpbqfy3i4sm37kk8g8s3d3l8j3-source/flake.nix, via option perSystem':1920       … while evaluating the option `system.build.toplevel':2122       … while evaluating definitions from `/nix/store/b8xf6hsi4wfakzvn6lsi040bh9n8djcc-source/nixos/modules/system/activation/top-level.nix':2324       … while evaluating the option `systemd.services.nginx.serviceConfig':2526       … while evaluating definitions from `/nix/store/b8xf6hsi4wfakzvn6lsi040bh9n8djcc-source/nixos/modules/system/boot/systemd.nix':2728       … while evaluating the option `systemd.services.nginx.preStart':2930       … while evaluating definitions from `/nix/store/b8xf6hsi4wfakzvn6lsi040bh9n8djcc-source/nixos/modules/services/web-servers/nginx/default.nix':3132       (stack trace truncated; use '--show-trace' to show the full, detailed trace)3334       error: Refusing to evaluate package 'jitsi-meet-1.0.9365' in /nix/store/b8xf6hsi4wfakzvn6lsi040bh9n8djcc-source/pkgs/by-name/ji/jitsi-meet/package.nix:61 because it is marked as insecure3536       Known issues:37        - The libolm end‐to‐end encryption library used in many Matrix38       clients and Jitsi Meet has been deprecated upstream, and relies39       on a cryptography library that has known side‐channel issues and40       disclaims that its implementations are not cryptographically secure41       and should not be used when cryptographic security is required.4243       It is not known if the issues can be exploited over the network in44       practical conditions. Upstream does not believe such an attack is45       feasible, but has stated that the library should not be used going46       forward, and there are no plans to move to another cryptography47       implementation or otherwise further maintain the library at all.4849       You should make an informed decision about whether to override this50       security warning, especially if you critically rely on end‐to‐end51       encryption. If you don’t care about that, or don’t use the Matrix52       functionality of a multi‐protocol client depending on libolm,53       then there should be no additional risk.5455       Some clients are investigating migrating away from libolm to maintained56       libraries without known vulnerabilities.5758       For further information, see:5960       * The CVE records for the known vulnerabilities:6162         * CVE-2024-4519163         * CVE-2024-4519264         * CVE-2024-451936566       * The libolm deprecation notice:67         <https://gitlab.matrix.org/matrix-org/olm/-/blob/6d4b5b07887821a95b144091c8497d09d377f985/README.md#important-libolm-is-now-deprecated>6869       * The warning from the cryptography code used by libolm:70         <https://gitlab.matrix.org/matrix-org/olm/-/blob/6d4b5b07887821a95b144091c8497d09d377f985/lib/crypto-algorithms/README.md>7172       * The blog post disclosing the details of the known vulnerabilities:73         <https://soatok.blog/2024/08/14/security-issues-in-matrixs-olm-library/>7475       * The statement about the deprecation and vulnerabilities from the76         Matrix.org Foundation:77         <https://matrix.org/blog/2024/08/libolm-deprecation/>7879       * A (likely incomplete) aggregation of client tracking issue links:80         <https://github.com/NixOS/nixpkgs/pull/334638#issuecomment-2289025802>818283       You can install it anyway by allowing this package, using the84       following methods:8586       a) To temporarily allow all insecure packages, you can use an environment87          variable for a single invocation of the nix tools:8889            $ export NIXPKGS_ALLOW_INSECURE=19091          Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,92                then pass `--impure` in order to allow use of environment variables.9394       b) for `nixos-rebuild` you can add ‘jitsi-meet-1.0.9365’ to95          `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,96          like so:9798            {99              nixpkgs.config.permittedInsecurePackages = [100                "jitsi-meet-1.0.9365"101              ];102            }103104       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add105          ‘jitsi-meet-1.0.9365’ to `permittedInsecurePackages` in106          ~/.config/nixpkgs/config.nix, like so:107108            {109              permittedInsecurePackages = [110                "jitsi-meet-1.0.9365"111              ];112            }