I am pulling/fetching from https but pushing through ssh.
The ssh key is set up and matches the fingerprint on my account, but I get timeout error.
What gives?
Evert Elias Andonovchanged fields9 months ago
Name
Previous Value
Current Value
Type
Bug
Task
Evert Elias Andonov commented 9 months ago
Okay, I've switched to https remote and it works fine.
Does it mean ssh remotes do not work?
honcho commented 9 months ago
Right, sorry, SSH isn't available. I could get it working if needed, kinda held up with other business at the moment though.
Evert Elias Andonov commented 9 months ago
Is it going to be available or not?
SSH is by far the easiest way to work securely with git. The other methods either store login and password in plain text somewhere or go through platform-dependant procedures for secure storage. Not to mention public keys can be revoked at any moment without going through password reset procedure.
So yes, it is needed, unless ssh server will explode the PC on which repo is hosted on.
honcho commented 9 months ago
I see, apologies. I just fixed SSH access. You should be able to get through to it on port 6611.
So I've created a fork and wanted to create a branch within for a test.
My current remotes (
git remote --verbose
) are looking like this:I am pulling/fetching from https but pushing through ssh.
The ssh key is set up and matches the fingerprint on my account, but I get timeout error.
What gives?