Skip to content

Detect Broadcom ControlVault fingerprint readers - #9510

Closed
zerone0x wants to merge 1 commit into
omacom:quattrofrom
zerone0x:fix/broadcom-controlvault-fingerprint
Closed

zerone0x wants to merge 1 commit into
omacom:quattrofrom
zerone0x:fix/broadcom-controlvault-fingerprint

Conversation

@zerone0x

Copy link
Copy Markdown

Summary

  • add Broadcom vendor ID 0a5c to the fingerprint-reader allowlist
  • cover the Dell ControlVault 3 0a5c:5843 device in the hardware detector tests

Fixes #9507

Testing

  • bash test/shell.d/hw-fingerprint-test.sh
  • bash -n bin/omarchy-hw-fingerprint test/shell.d/hw-fingerprint-test.sh
  • git diff --check
  • ./test/cli (metadata checks passed; the host then stopped at the existing python: command not found dependency)

@zerone0x

zerone0x commented Sep 1, 2026

Copy link
Copy Markdown
Author

Closing as a duplicate of #8486, which already implements the same Broadcom vendor allowlist and regression test. The existing PR also contains maintainer-facing analysis of false positives and TOD driver support, so keeping a second equivalent change open would add noise.

@zerone0x zerone0x closed this Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

omarchy-hw-fingerprint doesn't detect Dell ControlVault 3 (Broadcom BCM58200, vendor 0a5c)

1 participant