Key Signing follow up, what shall I do next?

So I attend the Key Signing party, exchanged my signatures, and even get emails telling me that my key is signed. I'm now a bit lost on what shall I do next, and trying to google for the answer didn't help much either. The closest I found is: GPG Tutorial https://futureboy.us/pgp.html#UpdatingKeys and I've checked the following sections: Updating Keys People are constantly updating their keys for various reasons: - Keys get compromised or lost and they are revoked. - Keys are signed by more people, building a Web of Trust <https://futureboy.us/pgp.html#WebOfTrust>. . . Who Signed My Key? Now that you've updated keys from a keyserver, you might want to see who has signed your key. After all, *anyone* can sign *any* key and re-upload that key to a key server. You can see the signatures with the --list-sigs command to gpg . . . However, I'm still at lost understanding them. I.e., I tried both the suggested commands, but can't see any sign that my key is signed by more people, and any of their emails. All that I know is that - I get an email telling me that my key is signed. - I'm able to decrypt it, and see an attachment of mykey.asc: --------------B954318AC305B6429BF6150D Content-Type: text/plain; charset=UTF-8; name="mykey.asc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="mykey.asc" What steps I shall do next? (Instruction for the command line is more welcome than using GUI) Thanks!

On Wednesday, April 18 2018, Antonio Sun via talk wrote:
So I attend the Key Signing party, exchanged my signatures, and even get emails telling me that my key is signed.
I'm now a bit lost on what shall I do next, and trying to google for the answer didn't help much either.
Hey Antonio, Basically, the person who signed your key (assuming that he followed the good practices) will have your key e-mailed to you in the ASCII armored format. You will need to save this file on your computer, import it using: gpg2 --import FILE and then verify that the new signature(s) are OK, using the "--list-signatures" option. After you've verified that everything is OK, you will then need to upload your key to a keyserver: gpg2 --send-key YOUR_KEY_ID --keyserver hkps://hkps.pool.sks-keyservers.net And that's basically it. I strongly suggest you read about OpenGPG best practices here: <https://riseup.net/en/security/message-security/openpgp/best-practices> It's important to read and understand them; your key will be used to identify you, so you need to keep it in good shape. By the way, I'm still waiting for your encrypted e-mail regarding the problem with your key IDs. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/

Thanks a lot Sergio. I've read the openpgp/best-practices <https://riseup.net/en/security/message-security/openpgp/best-practices> before, but it doesn't cover what to I do next after Key Signing party part. Thanks for the explanation. On Thu, Apr 19, 2018 at 1:24 PM, Sergio Durigan Junior - sergiodj@sergiodj.net wrote:
I strongly suggest you read about OpenGPG best practices here:
<https://riseup.net/en/security/message-security/openpgp/best-practices>
It's important to read and understand them; your key will be used to identify you, so you need to keep it in good shape.
By the way, I'm still waiting for your encrypted e-mail regarding the problem with your key IDs.
Yeah, I'm still in the process of finding what the correct way of doing things now. will do soon. Thanks

On Friday, April 20 2018, Antonio Sun via talk wrote:
Thanks a lot Sergio. I've read the openpgp/best-practices <https://riseup.net/en/security/message-security/openpgp/best-practices> before, but it doesn't cover what to I do next after Key Signing party part. Thanks for the explanation.
No problem, Antonio.
On Thu, Apr 19, 2018 at 1:24 PM, Sergio Durigan Junior - sergiodj@sergiodj.net wrote:
I strongly suggest you read about OpenGPG best practices here:
<https://riseup.net/en/security/message-security/openpgp/best-practices>
It's important to read and understand them; your key will be used to identify you, so you need to keep it in good shape.
By the way, I'm still waiting for your encrypted e-mail regarding the problem with your key IDs.
Yeah, I'm still in the process of finding what the correct way of doing things now. will do soon.
Sure, no problem at all. When we get this sorted out I'll gladly sign the key and you can proceed with the Debian Maintainer process. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
participants (2)
-
Antonio Sun
-
Sergio Durigan Junior