|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I dutifully created a GPG key last October, and that was how I got my
Object Collection uploaded to GitHub. I have been unable to do a single
damn thing with GitHub ever since, but I never posted my new
frustrations here before that initial key expired.
Now, the Git push will not accept my new key, which I created under
instruction from GitHub. It keeps asking for my old expired key. I
can't figure out how to get it to accept the new key. I'm effectively
locked out of my GitHub account.
The security seems to be handled by kwallet on my GNU/Linux/KDE system.
I have never been able to figure out how kwallet works.
I DON'T UNDERSTAND HOW ANY OF THIS SHIT WORKS!
Is my life getting easier yet?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Cousin Ricky <ric### [at] yahoocom> wrote:
> I dutifully created a GPG key last October, ...
> The security seems to be handled by kwallet on my GNU/Linux/KDE system.
> I have never been able to figure out how kwallet works.
on my machines GPG keys are stored in '~/.gnupg/', but I do not use KDE.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2022-01-23 13:48 (-4), jr wrote:
>
> on my machines GPG keys are stored in '~/.gnupg/', but I do not use KDE.
I found that directory. What do I do with it?
I see a couple of files that are time-stamped with the dates from my
first key last October, plus a bunch of other stuff that I don't know
what to do with.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Cousin Ricky <ric### [at] yahoocom> wrote:
> On 2022-01-23 13:48 (-4), jr wrote:
> > on my machines GPG keys are stored in '~/.gnupg/', but I do not use KDE.
>
> I found that directory. What do I do with it?
>
> I see a couple of files that are time-stamped with the dates from my
> first key last October, plus a bunch of other stuff that I don't know
> what to do with.
I guess you'll also have found the 'gpg' program? you can list keys + could
export the one you need. how you then use that with GitHub, no idea.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2022-01-23 16:00 (-4), jr wrote:
>
> I guess you'll also have found the 'gpg' program? you can list keys + could
> export the one you need. how you then use that with GitHub, no idea.
I did not realize such a program existed, but I just checked, and the
program is on my system. I did a gpg -k, and other than my email
address, I have no idea what I'm looking at.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoocom> wrote:
> I dutifully created a GPG key last October, and that was how I got my
> Object Collection uploaded to GitHub. I have been unable to do a single
> damn thing with GitHub ever since, but I never posted my new
> frustrations here before that initial key expired.
>
> Now, the Git push will not accept my new key, which I created under
> instruction from GitHub. It keeps asking for my old expired key. I
> can't figure out how to get it to accept the new key. I'm effectively
> locked out of my GitHub account.
>
> The security seems to be handled by kwallet on my GNU/Linux/KDE system.
> I have never been able to figure out how kwallet works.
>
> I DON'T UNDERSTAND HOW ANY OF THIS SHIT WORKS!
>
> Is my life getting easier yet?
What operating system are you using ?
Are you able to log into to your account via the GitHub web interface ? Here:
https://github.com/your-account-name
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
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.
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):
ssh-keygen -t rsa -b 4096
You need to upload the contents of "id_rsa.pub".
It will be here in Linux:
~/.ssh/id_rsa.pub
- and perhaps here in Windows 10/11:
%USERPROFILE%\.ssh\id_rsa.pub
There's some more information here:
"SSH keypair setup for GitHub (or GitHub/GitLab/BitBucket, etc, etc)"
https://gist.github.com/xirixiz/b6b0c6f4917ce17a90e00f9b60566278
If you have a not-so-recent Windows 10 installation, you may have to enable the
optional OpenSSH client.
--
Tor Olav
http://subcube.com
https://github.com/t-o-k
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Cousin Ricky <ric### [at] yahoocom> wrote:
> On 2022-01-23 16:00 (-4), jr wrote:
> >
> > I guess you'll also have found the 'gpg' program? you can list keys + could
> > export the one you need. how you then use that with GitHub, no idea.
>
> I did not realize such a program existed, but I just checked, and the
> program is on my system. I did a gpg -k, and other than my email
> address, I have no idea what I'm looking at.
(ah, there you have me. I cannot look at your screen. :-))
I trust you've solved your problem by now, if not:
$ gpg --list-keys
you should see which key you're after by looking at the 3rd (space-separated)
field, the date of creation. 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
never needed to do this, so check out the export comments re '-armor' option and
sending keys.
<https://www.gnupg.org/gph/en/manual.html>
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).
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |