From 81f91dafe4dc8548b653fc5d5bcb122c5f42da42 Mon Sep 17 00:00:00 2001 From: Charlie O'Keefe Date: Tue, 3 Nov 2020 15:06:59 -0700 Subject: [PATCH] change 'gpg2' to 'gpg' --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d734c16..35f630c 100644 --- a/README.md +++ b/README.md @@ -482,7 +482,7 @@ it makes sense in this case to upload there. You can upload your public key like this: ``` -$ gpg2 --keyserver pgp.mit.edu --send-keys 3F14A629C06FA31D59C64FE93F0C2117D53A4A49 +$ gpg --keyserver pgp.mit.edu --send-keys 3F14A629C06FA31D59C64FE93F0C2117D53A4A49 gpg: sending key 3F0C2117D53A4A49 to hkp://pgp.mit.edu ``` @@ -499,7 +499,7 @@ Some explanation of the arguments used in the above example: You can verify that the key was successfully uploaded like this: ``` -$ gpg2 --keyserver pgp.mit.edu --receive-keys 3F14A629C06FA31D59C64FE93F0C2117D53A4A49 +$ gpg --keyserver pgp.mit.edu --receive-keys 3F14A629C06FA31D59C64FE93F0C2117D53A4A49 gpg: key 3F0C2117D53A4A49: "Harry Potter (zcash gitian) " not changed gpg: Total number processed: 1 gpg: unchanged: 1