Package Details: trezor-bridge-bin 2.0.30-3

Git Clone URL: (read-only, click to copy)
Package Base: trezor-bridge-bin
Description: Communication daemon for TREZOR
Upstream URL:
Keywords: trezor-bridge trezord
Licenses: LGPL3
Conflicts: trezor-suite-appimage, trezor-udev, trezord-git, trezord-go
Provides: trezor-bridge, trezor-udev, trezord
Submitter: jugs
Maintainer: cga
Last Packager: cga
Votes: 24
Popularity: 0.26
First Submitted: 2015-08-07 01:06
Last Updated: 2021-06-09 17:15

Latest Comments

1 2 3 Next › Last »

cga commented on 2021-06-09 17:18

@natlu2809 I'm glad you solved your issue. Let's wait for upstream.

@akeller no time to do that right now. It seems many packages don't do that tho. I'm open to pointers and docs.

@louielu arm64 added with -3 version. let me know if it works please.

akeller commented on 2021-05-28 07:01

PGP verification could be part of this install. Right now, the package host is a single point of failure, and the only way to double check that the .deb is authentic is to import the PGP key for SatoshiLabs and run dpkg-sig yourself. We could add dpkg-sig as a dependent package (or as a source, since it is part of the git repo). Adding the PGP key could be a pain, but the fingerprint is at least listed on Github.

louielu commented on 2021-05-11 02:46

To support arm64 (e.g. pinebook pro) arch, we can add this to the PKGBUILD:

arch=('i686' 'x86_64' 'aarch64')



natlu2809 commented on 2021-05-09 14:42

to answer my own Q on 2021-04021 16:03 - Trezor support tell me :

"This is an issue with a third-party tool pamu2fcfg. Please keep in mind that we do not develop nor maintain third-party software, so we cannot guarantee their full functionality. However, your private keys are always safely protected by your Trezor device, no matter what third-party application you use it with.

The issue was already fixed ( but was not released yet. It is up to the third party to release the fix."

natlu2809 commented on 2021-04-21 16:03

Tell me to go somewhere else for support but Im having trouble with Trezor Model T and pam authn. pamu2fcfg is giving me an error: error: fido_cred_verify (-7) FIDO_ERR_INVALID_ARGUMENT. Installed this version 2.0.30-2 yesterday.

Any ideas, suggestions?

cga commented on 2021-03-19 10:05


I agree with you on the diff about udev, and I would fix that if I could. However this bin package uses a .deb archive, hence udev rules come from upstream. If this was a source based package I would fix this, but it's not.

bradwood commented on 2021-03-14 14:13

The udev rules on trezor's site are ever-so-slightly different to the ones shipped from this package

vimdiff <(curl /usr/lib/udev/rules.d/50-trezor.rules

Not sure if this is a problem or not, but would be nice to fix -- I've been having all kinds of bridge/LIBUSB errors and was wondering if this could be related.

cga commented on 2021-02-28 08:35

done :)

ipha commented on 2021-02-28 03:11

Could you add trezor-udev to provides? I'd like to have this installed alongside trezor-suite.

cga commented on 2020-11-20 18:50

I've successfully packaged it and installed it on my system. Here's the PKGBUILD:

# Maintainer: Jakub Trnka <>
# Contributor: Sebastian Jug <>

pkgdesc="Communication daemon for TREZOR"
arch=('i686' 'x86_64')
provides=('trezor-bridge' 'trezord')
conflicts=('trezord-git' 'trezord-go' 'trezor-udev')

package() {
    echo "Extracting the data..."
    bsdtar -xf data.tar.gz -C "$pkgdir/"

    echo "Fixing file structure..."
    mv "$pkgdir"/lib/udev "$pkgdir"/usr/lib/

    echo "Cleaning up..."
    rm -r "$pkgdir"/lib/

ps: I'm a veteran Arch/Linux - user/professional. I used to maintain a few AUR packages way back when. I'm now back to Arch and would be happy to maintain this one.