hwdb.d/70-hardware-wallets.hwdb

# This file is part of systemd.
#
# Database for Hardware Wallets that should be accessible to the seat owner.
#
# The lookup keys are $MODALIAS strings, see udev's hwdb builtin.
#
# To add local entries, create a new file
#   /etc/udev/hwdb.d/71-hardware-wallets-local.hwdb
# and add your rules there. To load the new rules execute (as root):
#   systemd-hwdb update
#   udevadm trigger /dev/…
#
# If your changes are generally applicable, send them as a pull request to
#   https://github.com/systemd/systemd
# or create a bug report on https://github.com/systemd/systemd/issues and
# include your new rules, a description of the device, and the output of
#   udevadm info
# for the device.
#
# Allowed properties are:
#   ID_HARDWARE_WALLET=0|1

################
# Trezor Hardware Wallets
################

# Trezor v1
usb:v534Cp0001*
 ID_HARDWARE_WALLET=1

# Trezor v2
usb:v1209p53C0*
 ID_HARDWARE_WALLET=1

usb:v1209p53C1*
 ID_HARDWARE_WALLET=1
add udev rules for trezor hw wallet devices 2024-07-22 22:57:25 +02:00			`# This file is part of systemd.`
			`#`
			`# Database for Hardware Wallets that should be accessible to the seat owner.`
hwdb.d: update/expand boilerplate on various hwdb files We don't want to encourage people to copy the whole files. The boilerplate text that recommends an override file rather than a full copy appeared first in 0213a26f656d72ac83eb201f2104726fcfe60eaa, but was added in other places in 57bb707d48131f4daad2b1b746eab586eb66b4f3. Directly inspired by 951e8cb06037d5b67c0ac86f56bcbd73f4fb2d7b, but the wrong boilerplate was added in other places too. 2025-05-14 17:44:25 +02:00			`#`
			`# The lookup keys are $MODALIAS strings, see udev's hwdb builtin.`
			`#`
			`# To add local entries, create a new file`
			`# /etc/udev/hwdb.d/71-hardware-wallets-local.hwdb`
add udev rules for trezor hw wallet devices 2024-07-22 22:57:25 +02:00			`# and add your rules there. To load the new rules execute (as root):`
			`# systemd-hwdb update`
hwdb.d: update/expand boilerplate on various hwdb files We don't want to encourage people to copy the whole files. The boilerplate text that recommends an override file rather than a full copy appeared first in 0213a26f656d72ac83eb201f2104726fcfe60eaa, but was added in other places in 57bb707d48131f4daad2b1b746eab586eb66b4f3. Directly inspired by 951e8cb06037d5b67c0ac86f56bcbd73f4fb2d7b, but the wrong boilerplate was added in other places too. 2025-05-14 17:44:25 +02:00			`# udevadm trigger /dev/…`
			`#`
			`# If your changes are generally applicable, send them as a pull request to`
			`# https://github.com/systemd/systemd`
			`# or create a bug report on https://github.com/systemd/systemd/issues and`
			`# include your new rules, a description of the device, and the output of`
			`# udevadm info`
			`# for the device.`
			`#`
			`# Allowed properties are:`
hwdb: say that settings can be also set to 0 We recommend that users create overriddes. This creates the problem that there is no syntax to unset a property. Thus, the user needs to just set the property to "something else" in the override file. But then the blurb saying that "VAR=1" (or "VAR=0" in some cases) is the only allowed value can be confusing. Say that both 0 and 1 can be set, since this documentation is also intended for end users. In our files, we generally don't want the override values anywhere. But we have a test which checks the rvalue, which should be enough. 2025-05-14 17:59:34 +02:00			`# ID_HARDWARE_WALLET=0\|1`
add udev rules for trezor hw wallet devices 2024-07-22 22:57:25 +02:00
			`################`
			`# Trezor Hardware Wallets`
			`################`

			`# Trezor v1`
			`usb:v534Cp0001*`
			`ID_HARDWARE_WALLET=1`

			`# Trezor v2`
			`usb:v1209p53C0*`
			`ID_HARDWARE_WALLET=1`

			`usb:v1209p53C1*`
			`ID_HARDWARE_WALLET=1`