4 ms·
I don't know what you mean by "encrypt per email address." Who is doing the encrypting, and to who? Do you want to have multiple keypairs associated with a sing
by coldpie 11y ago
I don't know what you mean by "encrypt per email address." Who is doing the encrypting, and to who? Do you want to have multiple keypairs associated with a single keybase account?
- realusername 11y agoYou can encrypt with lots of things, for example $> keybase encrypt twitter://twitter_id -m 'message' But there seems to be no way to to it with an email address like this: $> keybase encrypt email://email@example.org -m 'message' Or maybe I did not understand something.
- coldpie 11y agoYeah, email's a bit more complicated than twitter. I think for the time being, you want to just encrypt to a file and attach that. Maybe there's a standard (PGP mail?) that keybase could output to a file, but that doesn't tend to play well with the GUI mail clients that people typically use.
- realusername 11y agoThanks for your answer. The main goal on my case is to use the email address as an identity (since it's currently the closest thing I have for this) and not to send encrypted PGP email messages. That's why I never really understood keybase. You can encrypt with a twitter id but not send a encrypted tweet with GPG anyway, so why can't you encrypt by email ? I assumed the most basic form of identity is an email address. Thanks again for your answer.
- coldpie 11y agoWell, keybase only uses verified identities like twitter, hackernews, etc as identifiers. As far as I know, there's no way to publicly verify that someone actually owns an email address...
- deleted 11y ago[deleted]