Re: Using locate github

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Robert Moskowitz wrote:
> On 9/10/21 4:14 PM, Jonathan Billings wrote:
>> Any reason why you can't add your ssh pubkey to github?  You'll need
>> to change your remote from the git URI to a ssh URI.
> 
> I will have to figure out how to make a ssh key for my github userid...

At the risk of stating what you may already know, you don't
have to create a separate ssh key.

It's certainly not a bad idea to use different keys for
different systems, but it's not a requirement.

> I am guessing that in:
> 
> /home/rgm/data/htt/Projects/Critical/drafts/draft-ietf-drip-rid/.git
> 
> 
> I change
> 
> [remote "origin"]
>     url = https://github.com/ietf-wg-drip/draft-ietf-drip-rid
>     fetch = +refs/heads/*:refs/remotes/origin/*
> 
> to use ssh: rather than https:

The easier way (I think) is to use the git remote command to
change the URL.  It's not just a search https and replace
with ssh, so you'll want to take the URL from the GitHub
web interface.  It'll typically be something like this:

    git@xxxxxxxxxx:ietf-wg-drip/draft-ietf-drip-rid.git


To update that from the command line, you'd run:

    git remote set-url origin git@xxxxxxxxxx:ietf-wg-drip/draft-ietf-drip-rid.git

I'd second Jonathan and suggest that ssh is the simpler way
to go, but it should be possible to use the "personal access
tokens" with the git from Fedora 32 (that was 2.26.3, IIRC).
The PAT is essentially just a password, so it ought to work
the same way as before.

You can make the storage of such logins pretty painless
using a git credential helper.  On Fedora, the libsecret
helper should work with both Gnome and KDE (and others if
they support the "Secret Service" API).

This is in the git-credential-libsecret package.  With that
installed, you should be able to enable it via:

    git config credential.helper libsecret

That will enable it for the current repository.  (You can
enable it globally by adding --global after git config.)

Then you should be prompted for the username and password on
the next operation which requires it.  You'd use the PAT in
the password field and it should be stored in the Gnome
Keyring, KDE Wallet, or similar.

Having to type that out is one more reason I prefer using
ssh keys.  They're simpler to manage and useful in more
places.

HTH, and good luck on the overdue upgrade. :)

-- 
Todd

Attachment: signature.asc
Description: PGP signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux