Uploading private key via web interface and/or keybase client both don't let the user decide on their own encryption

I'm not sure if this is a documentation issue or implementation. If I'm uploading my secret key, it sounds as if it's encrypted but it's pretty opaque and not verifiable by the user. This is good for my parents but possibly frightening for the tinfoil hat crowd.

Is it not possible to upload a symmetrically encrypted private key and not provide any password whatsoever to keybase? Something like:
`gpg --export-secret-keys -a EF8FEBC949B9D15057F6D636102C7B498133F0FD | gpg --sign --symmetric --cipher-algo your_fav_cypher_here > seckey.gpg`

From the receiving client, you would wind up with a symmetrically encrypted blob that the user would have to decode before import:
`gpg --decrypt seckey.gpg | gpg --allow-secret-key-import --import`

Both of these steps should be automatable enough to do through the client and understandable enough for a user to copy/paste for a "hardcore mode" transfer.

Review the web interface and keybase client flows for uploading and importing private keys, then clarify whether this belongs in documentation or implementation. Define whether a user-controlled symmetrically encrypted transfer can avoid sharing a password with Keybase, and document or implement the agreed hardcore-mode workflow with an understandable completion criterion.

Written by the indexing model from the issue text.