methods to connect to GitHub: HTTPS or SSH?

[dhubs]

Dear friends, hello dear Linux-experts,


which methods do you use - and recommend?

what do you suggest - what is your use-case!?

do you (mainly) use SSH to connect to Github or some other sorts of source code-forge?

on the flipside: can we use https too!?

whats the appropiate way to connect to your repository?
What are the advantages or disadvantages of the both way and methods?


whats your opinion here?
eagerly look forward to your shared ideas and thoughts.

greetings


ps. some of my Friends say that using SSH makes working and contributing to projects a bit more comfortable and convenient as we don't have to type our username and password every time we want to push over HTTPS. ...

 

[f33dm3bits]

Public repositories I use https, private repositories I use ssh.

 

[CaffeineAddict]

ps. some of my Friends say that using SSH makes working and contributing to projects a bit more comfortable and convenient as we don't have to type our username and password every time we want to push over HTTPS. ...

That's exactly reason why I use only SSH.

Another advantage is you can cache your SSH key in DE dependent wallet such as KDE's KWallet or gnome-keyring for GNOME users.
What this means you never need to type your SSH password, it's unlocked together with your login.

 

[gvisoc]

From an user's perspective, I use them indistinctly. For HTTPS access, there's a GIT plugin that stores the username and personal access tokens in the Desktop Environment's credential manager, so they are almost the same. I have the actual plugin name in a note in my computer but now I'm AFK --but it works with gnome's and KDE's. The result is that once you set you up for a GIT server, you don't have to do anything until your personal access token expires(*)

From an owner's side of things (I self-hosf forgejo), the inconvenient that SSH has is that is harder to put it behind a reverse proxy and a WAF as you'd do with CloudFlare without having to hire a (very expensive) enterprise account. Hence in my own service I don't have enabled the possibility of logging on with SSH keys, and I use HTTPs instead.

(*): When talking about HTTPS, I use personal acceas tokens and not the service's password.

 

[gvisoc]

For HTTPS access, there's a GIT plugin that stores the username and personal access tokens in the Desktop Environment's credential manager, so they are almost the same. I have the actual plugin name in a note in my computer but now I'm AFK --but it works with gnome's and KDE's

I got the plugin: git-credential-libsecret.

• In fedora, there's a package ready to go: sudo dnf -y install git-credential-libsecret
• It will install in /usr/libexec/git-core/git-credential-libsecret
• Configure with git config --global credential.helper /usr/libexec/git-core/git-credential-libsecret

 

[MikeRocor]

you can cache your SSH key in DE dependent wallet such as KDE's KWallet or

Is this similar to what ssh-agent does?

 

[CaffeineAddict]

Is this similar to what ssh-agent does?

Slightly, KWallet stores SSH key password, which on my system is obtained with startup script which then runs ssh-add.

Another method is keychain package.