RE: Securely Generating an EOS Public / Private Key Pair Using Official EOS.IO Code

You are viewing a single comment's thread from:

Securely Generating an EOS Public / Private Key Pair Using Official EOS.IO Code

in eos •  7 years ago  (edited)

EOS's lack of standard key generation tool and offline registration instructions this close to launch is an embarassment and a disgrace. Key generation is the absolute base of any crypto system and underpines the entire future security model. With the current confusion around EOS registration and its near entire reliance on third party tools and instructions, for all we know most EOS registered wallets could already be compromised due to third party tools eavesdropping on keys, generating them with too little entropy or using a pseudo-random, reproductible key generation process.

As a very early supporter of Dan's work, I'm deeply disappointed by the careless approach taken by EOS.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

We share some of your sentiment. We can't speak for Block.One but we can do what we think is best by creating tutorials like these. Thank you for your feedback.

Keygen utility is provided by EOSIO project here https://github.com/EOSIO/genesis/tree/master/tools/keys and you can download pre-built executables (OSX only currently, Windows and Linux coming soon) here https://github.com/EOSIO/genesis/releases

Note that the executables are signed by Block.one.