with your answer I succed this part just now thank you
Unfortunately itās still not working but at list I fixed some issue with your help.
Maybe I will rebuild all this protocol from the beginning soon just in case i did something wrong
Maybe there is a problem with SELinux in fedora-39.
You can try to disable the SELinux for a test in the qubes by running this command:
sudo setenforce 0
And see if itāll work without it.
where i have to try this command line ? In dom0 or Fedora-39-Sys ?
In sys-usb.
Or you can try to use debian-12 template instead of fedora-39 template for sys-usb.
I tried now in sys-usb but nothing change
You can try to configure sys-usb to use debian-12 template for a test.
Hi Francois, I was wondering if you figured out how to get your Trezor runningā¦ I am running a very similar system (Nitrokey NV41, Qubes 4.2.1, debian 12, fedora 39, and whonix 17. I went through the process as described in the post and comments, but Iām not able to make it work. If you figured it out, can you please post it?
1 Like
Looks like a few people are having this issue. Iāll run through the process again and see if anything needs changing, and Iāll update this post with my findings.
In the meantime, please check out the in-depth guide at https://ursidaecyber.com. Itās more clear than the guide here and contains more details you may have missed.
1 Like
Thanks for this guide Ursidae. Iāve been using the In Depth Instructions and they are well written and easy to follow - Iām just not getting the final result I need. Iām looking forward to your revision.
1 Like
Also, on your page, someone asked about your reference in step 1 about needing a fresh whonix template to apply software. The commenter stated that there werenāt any references to adding software to the whonix template. You replied that it had to do with port listening. So should we be modifying the rc.local file in the whonix template in addition to the whonix AppVM?
Good question. I canāt answer that off the top of my head but Iāll take it into account when doing the revision.
Hi,
Unfortunately, I still havenāt managed to get Trezor to work on my system.
Iād like to reinstall everything again but I havenāt had the time
I just did but still not working
I did like that to install on debian:
Step 6: Trezor Bridge
In Debian-12-sys:
- Download the Trezor Bridge .deb file
- Open a terminal window in debian-12-sys and run the following code to allow the deb file to be executable:
sudo chmod u+x ./Downloads/trezor-bridge_2.0.27_amd64.deb - Install the Trezor bridge for debian file with the following code:
sudo apt install ./Downloads/trezor-bridge_2.0.27_amd64.deb
installation is maybe not perfect if you can read last line i had permission denied
Thatās not an error, you can ignore it.
I donāt have Trezor myself so I canāt check whatever the guide works or not, but maybe someone else can confirm that Trezor works on debian after following this guide. Then it should be an error on your side.
1 Like
I had the same problem, although I didnāt follow the howto to the letter as I donāt like messing with templates in general, but in the end I finally managed to get it to work.
I tried a lot of things, but the only way I was able to get this to work was by setting up trezord (trezor bridge that runs in sys-usb) to run as root instead of the trezord user as per the unit file. It seems that the non-privileged user doesnāt have full access to the trezor device, resulting in the trezor suite failing to detect it.
Ideally I would like to run this as a non-privileged user, but since sys-usb is disposable and has no network, I donāt see this as a major issue.
Hope this helps anyone else with a similar problem.
1 Like
the only way I was able to get this to work was by setting up trezord (trezor bridge that runs in sys-usb) to run as root instead of the trezord user as per the unit file.
Sorry to be such a newb, but how exactly did you do this?
1 Like
I guess you need to edit systemd service in the sys-usb template:
sudo systemctl edit trezord
or
sudo systemctl edit trezor
I donāt know how exactly the service is called, you can check it like this:
systemctl list-unit-files | grep -i trezor
Then find and edit the User= and maybe Group= options (or something similar) in systemd service file from trezord to root.
1 Like
That did the trick @apparatus - thank you!! Thanks also to @dak and @Ursidae !
@Francois : Iām pretty sure you and I are running identical hardware. This did the trick for me. Change āUser=trezordā to āUser=rootā in the trezord.service file of the sys-usb disposable. Mine was located in /usr/lib/systemd/system/
1 Like