trezor-suite
trezor-suite copied to clipboard
trezor
Trezor Suite not connecting from within Tails OS through TOR to Trezor Servers
Trezor Suite does not connect to Trezor servers trough Tails OS
- Remembered Wallet: yes
- Suite Version: 22.7.2 Linux Appimage
- Browser: Tails OS
- OS: Tails OS 5.2
- Bridge: sudo iptables -I OUTPUT -p tcp --dport 21325 -j ACCEPT -s localhost -d localhost sudo iptables -I INPUT -p tcp --dport 21325 -j ACCEPT -s localhost -d localhost
- Firmware Version: 2.5.1
Trezor Suite used to work very well from within Tails OS after running the "iptables" in a terminal and enabling traffic through the Tor network. Lately the suite does not connect to Trezor servers and its impossible to see the crypto addresses in the wallet.
The Suite tries to connect to Trezor servers but after approximately 30 seconds it fails. As you can see the Trezor T is connected (left upper corner of first screenshot), unfortunately the addresses are not visible.
Suggestion: Make Trezor Suit loadable through Synaptic Package Manager. Make Trezor Suit work through Tails OS/Tor in the same way as Electrum and Featherwallet. If Electrum.appimage works from within Tails OS Trezor should be able as well.
As both Trezor Suit and Tails OS has been updated recently I decided to run a test. Unfortunatelly the issue is still present. Trezor Suit can not connect to Trezor servers from within Tails OS.
Suite Version: 22.7.3 Linux Appimage Browser: TOR Browser 11.5.1 OS: Tails OS 5.3
Tried bridge: sudo iptables -I OUTPUT -p tcp --dport 21325 -j ACCEPT -s localhost -d localhost sudo iptables -I INPUT -p tcp --dport 21325 -j ACCEPT -s localhost -d localhost and sudo iptables -I OUTPUT 3 -o lo -s 127.0.0.1/32 -d 127.0.0.1/32 -p tcp --dport 21325 --syn -m owner --uid-owner amnesia -m conntrack --ctstate NEW -j ACCEPT
Both should make Trezor Suit connect but unfortunatelly thats not the case any longer.
Hope that gets resolved as well. https://github.com/trezor/trezor-suite/issues/6588
ISTM that Trezor Suite runs its own instance of Tor on (running on random port), but connecting to it is prevented by Ferm (Tails OS port firewall).
Is there a reason why we don't use the Tor daemon provided by the system (running on port 9050) if there is one already running? I vaguely remember we were doing that originally. @karliatto
For the record, here is the Tails OS Ferm config: https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-includes/etc/ferm/ferm.conf (basically list of enabled ports).
Is there a reason why we don't use the Tor daemon provided by the system (running on port 9050) if there is one already running? I vaguely remember we were doing that originally. @karliatto
@prusnak The reason we do not use the Tor daemon provided by the system is because we want to run it with ContolPort enable in order to be able to listen to the events that Tor emits so we can make it more stable for example when bootstraping, we make sure that we do not start any communication until Tor let us know that the circuits have been established and they are ready.
Thanks @karliatto for the answer.
I think Tor in Tails OS has ControlPort enabled, so in case system-provided daemon listens on 9050 (proxy) and 9051 (control port), we could just use that, right?
I think Tor in Tails OS has ControlPort enabled, so in case system-provided daemon listens on 9050 (proxy) and 9051 (control port), we could just use that, right?
It depends if the ControlPort run by Tail OS has CookieAuthentication or it does not have any authentication at all.
If it has CookieAuthentication and the user running trezor-suite has access to it (most likely in Tor default data directory) then yes.
We could check that Tor is running in 9050 (proxy) and that we can successfully connect to 9051 (ControlPort) using the default control_auth_cookie and use it.
It would be great if that works with the defaults for Tail OS.
Tried to get MyWallet working on Tails and Whonix to connect to Trezor Wallet. On Tails no Ethereum Network connection on MyCrypto. Therefore can't proceed further to detect Trezor Wallet. On Whonix there is connection to Ethereum Network on MyCrypto. But still Trezor Bridge doesnt work. Doesn't detect the Trezor. Same with Tor Browser on both OS and Windows also doesn't work.
That's a huge assertion, but maybe Trezor Team disabled all other functionality options that everyone needs to connect over their Suite App?
I just would like to have a possibility that Trezor is working on a Tor by default OS and/or connecting over Tor Browser.
Hope the Trezor Team is working on that! :)
Thanks!
Does anyone get the Trezor working on another OS than Windows?
On Tails doesn't work.
On Whonix I run on Terminal in the folder sudo dpkg -i trezor-bridge_2.0.27_amd64.deb and sudo dpkg -i trezor-udev_2_all.deb. Than open Suite and says ' Trezor Bridge not running '. I got a notification though that a new Version of Suite is available, but I dont get access to Tor when I want to connect at the switch. The Download starts. Tor Browser on Whonix also doesnt show up http://127.0.0.1:21325/ the Trezor device. So the Device doesnt get recognized on Whonix as well... and I dont get connection to Tor on Suite on Whonix.
On Whonix I can start the App 'MyCrypto' and I get connection to the Ethereum Network. Which doesn't work on Tails actually. Than I get asked ' How would you like to connect to your Wallet? ' There is Trezor listed. ' Connect to Trezor ' - no device connected. As the device doesnt get recognized on Whonix.
On Kali Linux, I see the http://127.0.0.1:21325/status/ page, but says connected Devices: 0 Also on Suite App it says ' Connect your Trezor '.
I would like to have the Trezor running on a Tor by default OS or Tor Browser.
For sure on Tails the Trezor works for Electrum. But what about others coins?
Just to have it running on Tor Browser would be the nicest option.
@Hercules1122 Please don't copy your comments to various issues.. it makes the job more complicated.
I would really like this to be resolved in someway - even some manual workaround or editing settings files but really you like this to work in tails
Still the same on the newly released Tails 6. I think that at least some workaround until fix would be nice. Tails and Trezor by design scream to work together.
Tails and Trezor by design scream to work together.
Electrum works with Trezor out of the box in Tails.
Tails and Trezor by design scream to work together.
Electrum works with Trezor out of the box in Tails.
Just tried, and unfortunately Tails 6 have incompatible versions of the two: Electrum says it wants a version of trezor 0.13 while installed there is a 0.12.4-2 !
Just tried, and unfortunately Tails 6 have incompatible versions of the two: Electrum says it wants a version of trezor 0.13 while installed there is a 0.12.4-2 !
I wrote an email to Debian maintainers, they do not update packages very often sadly. In the meantime you can try updating the trezor package from PyPI. Maybe sudo pip3 install trezor will work?
I wrote an email to Debian maintainers, they do not update packages very often sadly.
Did maintaners reply?
In the meantime you can try updating the trezor package from PyPI. Maybe
sudo pip3 install trezorwill work?
Tails do not use PIP. I tried to install it but aborted halfway since was requiring virtual environments and other things and not sure this is the way to go (and all the time the would have to be reinstalled).
Trezor Suite is still not working and Electrum/trezor packages versions are still mismatched...
There is someone that at least can suggest some workaround (e.g. how to properly install the trezor python library to be used by Electrum or some manual workaround to make Trezor suite working)? Surely will be appreciated!