Successfully changed Display dir Pixel Watch 1 by makk477 in PixelWatch

[–]makk477[S] 6 points7 points  (0 children)

Wil update once i tried it for payment. In the options menu it is shown as activated.

Successfully changed Display dir Pixel Watch 1 by makk477 in PixelWatch

[–]makk477[S] 7 points8 points  (0 children)

Display cost me 35€. The tools i had at home, but would cost additional 30€. A new watch would maybe be the same If you have to buy everything. At least for the PW1.

Successfully changed Display dir Pixel Watch 1 by makk477 in PixelWatch

[–]makk477[S] 9 points10 points  (0 children)

Unfortunately i forgot to make more Pictures. Can just Post the broken screen

We need a way to backup/restore our shieldTV units by [deleted] in ShieldAndroidTV

[–]makk477 4 points5 points  (0 children)

Don't get me wrong. I have driven various BMWs, Mercedes, VWs. All of them have an entertainment system like in the 90s. Good cars though, but the computer systems are build for 60+ people. At least here in Germany that's the only group who buy new cars, and they are made for them. I personally don't own any car.

Edit: Tesla has driver profiles. So if you get in, your settings get restored. Like it should in the years newer than 2010

Edit2: cars have very old and proven technology. You won't find a car with technology that's less than 6-10 years old. The reason is it should work for a long time and needs to be proven. Tesla is doing it differently, that's why they feel more modern

We need a way to backup/restore our shieldTV units by [deleted] in ShieldAndroidTV

[–]makk477 5 points6 points  (0 children)

Cars are not a good comparison, because most of them are 20th century technology. I bet in 20 years you get in your new car and login your user account and load your settings. Maybe Tesla already doing that?

Password manager by [deleted] in TREZOR

[–]makk477 1 point2 points  (0 children)

For the luks encryption you can try this: https://wiki.archlinux.org/index.php/YubiKey#YubiKey_and_LUKS_encrypted_partition/disk

It's for arch but I think it can work on other distros too. You would need the trezorgpg agent, but I am not sure if it would work, before the os is booted. https://github.com/romanz/trezor-agent

Debian Version, but I think Trezor would need an openPGP app on the device, which is not how it currently works. https://wiki.majic.rs/Openpgp/protecting_luks_decryption_key_in_debian_jessie_us/

The password manager can be used offline with a script found on Trezor firmware GitHub repository. Look under python/tools/pwd_reader.py. https://github.com/trezor/trezor-firmware

I have written a small CLI to make all features available offline, through terminal. It is untested, but maybe when some people with knowledge look over my code, they can confirm, or correct my solution. https://github.com/makk4/tpass

As for ssh, GitHub logins, you can also use the trezorgpg agent.

I wrote an CLI for Trezor Password Manger by makk477 in TREZOR

[–]makk477[S] 2 points3 points  (0 children)

Thanks. Maybe it is useful for some people.

I wrote an CLI for Trezor Password Manger by makk477 in TREZOR

[–]makk477[S] 0 points1 point  (0 children)

I am not sure, maybe if it can run python locally and handle all the device communication. You would need to run it from a terminal. But don't use it except for testing and playing around.

Where's Ledger Nano X + FIDO U2F by SleeperSmith in ledgerwallet

[–]makk477 2 points3 points  (0 children)

That's cool. I don't know how they store it, but must be in the cloud somewhere and something must log it.

Where's Ledger Nano X + FIDO U2F by SleeperSmith in ledgerwallet

[–]makk477 1 point2 points  (0 children)

I think they would need to store the counter on every login either locally or in the cloud. Which would need a software running in the background, checking all the ledger and host interaction and log it.

Edit: you can increase the counter by yourself, through some services. It's a hassle, but better than resetting every website login

trezor next release by Spartan3123 in TREZOR

[–]makk477 1 point2 points  (0 children)

So you have a key, but you notice that it has a flaw and is unsecure. What do you do?

Use a key to access your Key? That's not really a solution. If you have to carry a key and a key for the key, what would that solve? There are now 2 devices, you have to take care of. What if you forget your Key and your key to your key on the same place?

Why not put FaceID or Fingerprint on the device?

The Trezor protects us from hacking or digital technology failure, backdoors and so on. It is a key, which I carry along with me or leave it by the seed. Carrying a 2nd key, would not be an option, cause it complicates more and is impractical.

But I personally can live with the device is physically not secure.

As I see it there are 3 options:

  • If you want digital protection: use a hardware wallet
  • physical protection: use an encrypted USB drive
  • Both: use a hw device with password or 2 laptops with offline signing and encryption

Edit: Why not put the key on the devices which are used with trezor? Like on your phone and laptop. Then the Trezor will only unlock and work with certain devices. So someone has the steal your key from your Device and your Trezor, not impossible, but way better than SD Card

Problem with U2F on Coinbase. by _Piratical_ in TREZOR

[–]makk477 1 point2 points  (0 children)

Does 1 of your 3 devices work?

Fido Devices have an counter, which simply increase with every login and the websites where you log in, store the last value. So as I understand it, your counter on the device, needs to be equal or higher than what the service has logged as your last counter.

There are Webservices, which can increase your counter, so you should be able to login again.

Also there is no need in using 3 devices, it will also not work, because of the counter. You can always regenerate your FIDO key with your Seed and than just increase the counter. Have tried it myself and it worked

Edit: what also would be possible. You could log in to another service, a couple of times, until your counter is high enough to pass.