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:
If so, then you can go to this page to administrate the SSH and GPG keys
associated with your GitHub account:
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:
- and perhaps here in Windows 10/11:
There's some more information here:
"SSH keypair setup for GitHub (or GitHub/GitLab/BitBucket, etc, etc)"
If you have a not-so-recent Windows 10 installation, you may have to enable the
optional OpenSSH client.
Post a reply to this message