Post
Topic
Board Hardware wallets
Re: [ESHOP launched] Trezor: Bitcoin hardware wallet
by
slush
on 11/12/2014, 03:18:28 UTC
2) connected the Trezor device, SElinux alerts go off immediately the plug-in tries to run ... checking into details for the SEAlert gives a few options for allowing mozilla plugins correct access to root locations ... ok, w/e
Code:
SELinux is preventing /usr/lib64/firefox/plugin-container from write access on the chr_file .
just playing at this stage so not going to allow that for real until I think through what it is trying to do but play along since I'm not putting any coins anywhere near this until I understand it

This should be okay. SELinux rules obviously don't expect that browser should talk to USB...

Quote
3) device connects and immediately get a firmware is out-of-date message

This is also fine. We've released new firmware since we stocked this batch of devices.

Quote
that flashes up only long enough for me to read first two lines then disappears ... so need to keep disconnecting and reconnecting device until I can read the whole message ...

Well, this is definitely a bug. Could you please report this to support@bitcointrezor.com together with the output from the Javascript console? There's "show log" in right bottom corner of site which should do the job. Log will help us a lot.

Quote
4) connect device while holding down both buttons and page asks do I want to update firmware ... sure what else am I going to do, rewrite it myself? ...

Haha. The security question is there for obvious reason, so user cannot be guided by malicious software to bootloader mode without knowing that the firmware can be replaced without any further confirmation.

Quote
error message flashes up
Code:
Update Failed
b._session is null
and browser becomes very sluggish, cpu fan kicks in signifying usually a runaway process (most likely the mytrezor plugin I expect)

Hm, this may be related to previous issue with flickering dialog. As a temporary workaround, reloading the site and re-connecting the Trezor directly to bootloader mode (without letting the dialog about outdated firmware appear) might help. I know, it's definitely bug and we'll hunt it, but this may actually help instantly.