I can't find my public key

[fwermus]

Hi all,
I want to have my public key, but I can't. I generate the private key and I can see it. I am surprise I can't see my public key.

Actually the help is not saying anything about my public keys:

Welcome to mymail-crypt for Gmail!

Use the "my keys" section to generate a new OpenPGP key, import an existing key, or remove a key from the system. This manages private keys.
Use the "friends' keys" section to import or remove keys from your friends. This manages public keys
Use the "help" section for troubleshooting, and background information.
Make sure that you keep backup copies of all the keys you generate. If they're lost, they're lost.

Before using this extension please read the "help" page and be aware of the security concerns. Also please be aware that the license of this software clearly states this comes WITHOUT ANY WARRANTY.

thanks in advance

ps: one more: It is kind of confusing that the program's name is mymail-crypt and the project is named gmail-crypt. Am I missing something?

[seancolyer]

I'm sorry -- I don't quite understand your issue. You're asking where your public key is stored if you generate a new key?

The public key should be stored in the "Friends keys" section. Hm, I realize this might be a somewhat confusing title, but I find that people can have a hard time with things when they're named public keys. Maybe there's a better alternative?

The github repository is named gmail-crypt because this is what I originally wanted to call the extension, but the rules for posting to the Chrome Web Store indicate that naming it that way would be frowned upon by Google and likely result in its expulsion from the store.

Let me know if that helps.

[fwermus]

I don't understand and anyway I still can't see it. I generate a private
and public key. I can see my private key, but I need to share my public
key with my friends. I cannot see any link or place where I can see it,
which is strange.

Fernando Wermus.
fwermus.blogspot.com.ar/
twitter.com/fernandowermus

Los contenidos de este mensaje, y los archivos adjuntos, son de carácter
confidencial. Si ud. no es el legitimo destinatario de este mensaje, avise
inmediatamente al remitente y borre este mensaje. Cualquier distribución o
divulgación no autorizada de este mensaje y sus archivos asociados está
prohibida. Por favor infórmenos inmediatamente y destruya el original o
cualquier impresión del mismo.

Important Note:
This e-mail (including any attachments) is confidential and intended only
for the use of the addressee (s) named herein. If you have received this
e-mail in error, you are hereby notified that any review, copying or
distribution of it is strictly prohibited. Please inform us immediately and
destroy the original e-mail and any printouts.

On Sun, Jul 21, 2013 at 8:52 PM, Sean Colyer notifications@github.comwrote:

I'm sorry -- I don't quite understand your issue. You're asking where your
public key is stored if you generate a new key?

The public key should be stored in the "Friends keys" section. Hm, I
realize this might be a somewhat confusing title, but I find that people
can have a hard time with things when they're named public keys. Maybe
there's a better alternative?

The github repository is named gmail-crypt because this is what I
originally wanted to call the extension, but the rules for posting to the
Chrome Web Store indicate that naming it that way would be frowned upon by
Google and likely result in its expulsion from the store.

Let me know if that helps.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-21319531
.

[nejucomo]

I just found this ticket because I had the same issue. When I saw @seancolyer 's comment I realized I can find my pubkey and it's id under friends keys. Given that I found this issue ticket before I found that solution in the UI itself, I believe this usability issue needs to be addressed.

One possibility is to rename friends' keys to public keys.

Another solution which maintains the friends' keys page is to add a link under my keys which can also display the public key and it's associated ID.

<soapbox>
Being explicit and specific is more user friendly than trying to "sound friendly". For someone to properly use this extension, they must understand what private and public keys are, and how they are used differently, so the UI should not obscure these.

Following that principle, I also recommend renaming the friends' keys labels from key id to public key id and show key to show public key.
</soapbox>

Edit: Moved the soapbox stuff to the bottom and fixed formatting.

[UnsolvedCypher]

I think that putting the public key next to the private key under "my keys" might make it easier to use. It's clearly visible, and it's in the same place you would go for your private key.

[nyambol]

Note: if you want to add the generated key to your keyring, you need both public and private bits. One more reason to make explicit the connection.