Pages:
Author

Topic: If your Private Key's are compromised by manufacturer's of hardware wallet's !! - page 2. (Read 313 times)

legendary
Activity: 2212
Merit: 7064
As we know Private keys are generated only Once on every hardware wallet while setting up.
This is not exactly true, because you can generate new seed words as many times as you want if you reset your hardware wallet.
You can even import keys that you generated yourself, that can be much more secure and it won't be connected with flaws or random generation by devices.

How do we trust anything or anyone that it's a complete random generation, we are not in it we are trusting manufacturer's? It's like trusting third party?
Seed word generation in hardware wallets can be a issue but you are never exposing them to internet or broadcasting back to developers or anyone else (unless you received hacked malicious device.)
You don't have to trust anyone and you can use dices or cards to generate your own BIP39 words and them import that in your hardware wallet.
Each hardware wallet is doing entropy in different way and you can read more about that in one of my topics:
https://bitcointalksearch.org/topic/seed-generation-in-hardware-wallets-5317199

There maybe possibilities of having loopholes while connecting to software's how can we trust it if they are created under any force?
Nobody is forcing you to buy those devices or to trust anyone, but you can always choose open source hardware wallet projects that have been tested by security experts.
If you know the code you can always check everything yourself, but let's be realistic hardware wallets are no different from any other devices you use everyday like stupidphones for example.
legendary
Activity: 952
Merit: 1385
There maybe possibilities of having loopholes while connecting to software's how can we trust it if they are created under any force?

How manufacturer's come out of these issue's ? what should be the next invention to protect crypto for getting more decentralised.

"decentralised"?
Why does it worry you?
Do you wonder if ATM producer created a backdoor in the machine and may steal your money?
Do you wonder if airbag in your car will be launched correctly? (Yes, I know Tanaka case)

At the end they are producers/sellers - and no-one will buy compromised devices. That's why they fix issues, they publish firmware updates etc.
legendary
Activity: 2730
Merit: 7065
Why do you bring this question up only for hardware wallets? When we are speaking of trust, why would you trust Bitcoin Core, Electrum, or any of the developers who has ever worked on Bitcoin including Satoshi?

Use open-source and verifiable software. Check the source code personally if you know how to. If you don't, you have no other choice but to trust that others have done it. The more people that have done independent reviews, the better. But for must people who have no idea how computer code works, you have no other source but to trust what other security experts have checked and reported.   
member
Activity: 126
Merit: 10
As we know Private keys are generated only Once on every hardware wallet while setting up.

We can't generate it many times or as we want, if that fixed one generation of key while setting up every hardware wallet are already compromised?

How do we trust anything or anyone that it's a complete random generation, we are not in it we are trusting manufacturer's? It's like trusting third party? If any force make them cheat on it how can we protect ourself because people are trusting hardware wallets blindly thinking its 100% safe many have lifetime saving's on it !!  

There maybe possibilities of having loopholes while connecting to software's how can we trust it if they are created under any force?

How manufacturer's come out of these issue's ? what should be the next invention to protect crypto for getting more decentralised.

Questioning is the only right way, we should focus on appreciating questions to bring crypto to next level.


Disclaimer: OP is not attacking or blaming anyone, it's just a question nothing else.    
Pages:
Jump to: