build: silence udevCheckHook in nix-shell, there are no udev rules to check
What the developer wrote
Authored by Andrew Kozlik
build: silence udevCheckHook in nix-shell, there are no udev rules to check
What changed, and why it matters
This commit adds a single build configuration line to the project's Nix shell environment. It simply stops a harmless informational message ('Using udevCheckHook') from being printed during setup, because there are no udev device rules present to validate. There is no security issue here.
No security action needed. This is a cosmetic build-environment change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change sets dontUdevCheck = 1 in shell.nix. In Nix, udevCheckHook is a setup hook that prints a notice when packages containing udev rules are included. Since the Trezor firmware shell environment has no udev rules to check, the hook output is noise. The commit silences that noise. It does not alter udev rules, disable a security check, change permissions, or affect firmware/runtime behavior.
Changed components
shell.nix (development environment configuration)Inspect captured patch +2 / −0
diff --git a/shell.nix b/shell.nix
index 1a652587..cf4e0400 100644
--- a/shell.nix
+++ b/shell.nix
@@ -165,6 +165,8 @@ stdenvNoCC.mkDerivation ({
# Enabling rust-analyzer extension in VSCode
RUST_SRC_PATH = "${rustProfiles.rust-src}/lib/rustlib/src/rust/library";
+ # Avoid printing "Using udevCheckHook", there are no rules to check
+ dontUdevCheck = 1;
} // (lib.optionalAttrs fullDeps) {
TREZOR_MONERO_TESTS_PATH = moneroTestsPatched;
})
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.