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