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.
RE: Securely Generating an EOS Public / Private Key Pair Using Official EOS.IO Code