On 2022-01-23 21:01 (-4), Tor Olav Kristensen wrote:
> 
> What operating system are you using ?

openSUSE Leap 15.5 GNU/Linux

> Are you able to log into to your account via the GitHub web interface ? Here:
> 
> https://github.com/your-account-name

Yes.

> If so, then you can go to this page to administrate the SSH and GPG keys
> associated with your GitHub account:
> 
> https://github.com/settings/keys

Yes.  Strangely, is says there are no keys associated with my account.
So where are all those keys I had been setting up through the link that
GitHub emailed to me every month?

> You can try to add another key. If you are using Linux or Windows 10/11 or
> MacOS, then I suggest that you add a new SSH key to your GitHub account.

I was using GPG because that's what was in the instructions I got from
GitHub after they discontinued password pushing.  Are there advantages
or disadvantages to one system over the other?

Thanks for your attention.

Post a reply to this message

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

hi,

Cousin Ricky <ric### [at] yahoocom> wrote:
> 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.

:-)


> > ...
> >  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.

I have no use for 'gpg' apart from s/ware downloads/installs.  but this is what
I see, for the distribution's key:

root@crow:~# gpg --version
gpg (GnuPG) 1.4.21
  ...

root@crow:~# gpg --list-keys
/root/.gnupg/pubring.gpg
------------------------
pub   1024D/40102233 2003-02-26 [expires: 2038-01-19]
uid                  Slackware Linux Project <sec### [at] slackwarecom>
sub   1024g/4E523569 2003-02-26 [expires: 2038-01-19]

not sure why the format of the second field differs.  sorry.


regards, jr.

Post a reply to this message

On 2022-01-30 12:30 (-4), jr wrote:
> 
> Cousin Ricky <ric### [at] yahoocom> wrote:
>>
>> I see no slash anywhere in the output.
> 
> I have no use for 'gpg' apart from s/ware downloads/installs.  but this is what
> I see, for the distribution's key:
> 
> root@crow:~# gpg --version
> gpg (GnuPG) 1.4.21
>   ...
> 
> [snip]
> 
> not sure why the format of the second field differs.  sorry.

My version of gpg is 2.2.27.

Do you normally work as root?

Post a reply to this message

hi,

Cousin Ricky <ric### [at] yahoocom> wrote:
> On 2022-01-30 12:30 (-4), jr wrote:
> ...
> > root@crow:~# gpg --version
> > gpg (GnuPG) 1.4.21
> >   ...
>
> My version of gpg is 2.2.27.

still, I'd have expected a comparable output.


> Do you normally work as root?

no.  I had to log in because root is the only account with a '~/.gnupg/' (for OS
updates), it's 'ssh' for everything (and everyone) else.


regards, jr.

Post a reply to this message

hi,

(sorry, just occurred to me)

Cousin Ricky <ric### [at] yahoocom> wrote:
> ...
> 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.

have you checked whether there are other 'pubring.{kbx,gpg}' files anywhere?
thinking KDE might store stuff in places other than just your user's home.  I'd
use 'locate(1)' though 'find(1)' will do.


regards, jr.

Post a reply to this message

On 2022-01-23 21:01 (-4), Tor Olav Kristensen wrote:
> 
> A private and a public ssh key can be created e.g. like this both in Linux,
> MacOS and a recent Windows 10 (and perhaps in Windows 11):
> 
>     [snip]

OK, I created an SSH key and followed GitHub's instructions for adding
it to my ssh-agent, re-created the remote origin reference on my local
repo, and tried to push again.  Git-Cola *still* asked for the damn
expired GPG key.

I guess I'll have to dig out the instructions on how to push from the
CLI, and see if that works.  But like I said before, I cannot remember
these commands from one moment to the next; but I do remember that if I
forget a step, or if I omit or get one of the myriad command line
switches wrong, none of it will work.

Is my workflow getting easier yet?

Post a reply to this message

Cousin Ricky <ric### [at] yahoocom> wrote:
>
> OK, I created an SSH key and followed GitHub's instructions for adding
> it to my ssh-agent, re-created the remote origin reference on my local
> repo, and tried to push again.  Git-Cola *still* asked for the damn
> expired GPG key.
>
> I guess I'll have to dig out the instructions on how to push from the
> CLI, and see if that works.  [snip]

The push worked from the CLI.  Next is to find out why Git-Cola is still stuck
in the past.

Post a reply to this message

"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> Cousin Ricky <ric### [at] yahoocom> wrote:
> >
> > OK, I created an SSH key and followed GitHub's instructions for adding
> > it to my ssh-agent, re-created the remote origin reference on my local
> > repo, and tried to push again.  Git-Cola *still* asked for the damn
> > expired GPG key.
> >
> > I guess I'll have to dig out the instructions on how to push from the
> > CLI, and see if that works.  [snip]
>
> The push worked from the CLI.  Next is to find out why Git-Cola is still stuck
> in the past.

Good.

Do you know what key (GPG or SSH) was being used when it worked from the command
line ?

If it was not the SSH key; did you paste the contents of the id_rsa.pub file
into the key field at this page:

https://github.com/settings/ssh/new

Btw.: I had to google Git-Cola to find out what it is. I wasn't aware that you
use it. I haven't used such GUI tools myself, just the git tools on the command
line and the web interface at github.com.

--
Tor Olav
http://subcube.com
https://github.com/t-o-k

Post a reply to this message

On 2022-01-31 21:02 (-4), Tor Olav Kristensen wrote:
> "Cousin Ricky" <rickysttATyahooDOTcom> wrote:
>> Cousin Ricky <ric### [at] yahoocom> wrote:
>>>
>>> OK, I created an SSH key and followed GitHub's instructions for adding
>>> it to my ssh-agent, re-created the remote origin reference on my local
>>> repo, and tried to push again.  Git-Cola *still* asked for the damn
>>> expired GPG key.
>>>
>>> I guess I'll have to dig out the instructions on how to push from the
>>> CLI, and see if that works.  [snip]
>>
>> The push worked from the CLI.  Next is to find out why Git-Cola is still stuck
>> in the past.
> 
> Good.
> 
> Do you know what key (GPG or SSH) was being used when it worked from the command
> line ?

It was SSH.

> 
> Btw.: I had to google Git-Cola to find out what it is. I wasn't aware that you
> use it. I haven't used such GUI tools myself, just the git tools on the command
> line and the web interface at github.com.

Fortunately, Git-Cola and the CLI work well together.  I can switch back
and forth at any time, and the Git repos maintain their integrity.

Post a reply to this message