On 2022-01-24 04:20 (-4), jr wrote:
> 
> I trust you've solved your problem by now,

Of course not!  Whatever gave you that idea?  I was just taking a break
from the frustration.

> if not:
> 
>   $ gpg --list-keys

----------[BEGIN SCREEN OUTPUT]----------
/home/ricky/.gnupg/pubring.kbx
------------------------------
pub   rsa2048 2021-10-06 [SCEA]
      SomeBigNumberIDontThinkIShouldPostHere
uid           [ultimate] Ricky <my### [at] emailaddress>
sub   rsa2048 2021-10-06 [SEA]
-----------[END SCREEN OUTPUT]-----------

> you should see which key you're after by looking at the 3rd (space-separated)
> field, the date of creation.

The date I'm seeing is for the long-expired key from last October.  I
see no sign of the keys that GitHub had me set up since.

>  its first field should read 'pub'(lic).  the
> second field is a slash separated compound, use the number after the slash to:
> 
>   $ gpg --export theNumber > the_file_to_use_on_github

I see no slash anywhere in the output.

> 
> fwiw, TOK's ""SSH keypair setup for GitHub" link looks v good.  had not known
> you can use ssh keys too, recommend you switch from 'gpg' to 'ssh' at some point
> (easier to use + manage).

I guess I'll look into it... I guess.  If I switch over, will it confuse
GitHub?

Thanks for trying to help out.

Post a reply to this message