
-
Name Previous Value Current Value Type
Bug
Task
-
Okay, I've switched to https remote and it works fine.
Does it mean ssh remotes do not work? -
Right, sorry, SSH isn't available. I could get it working if needed, kinda held up with other business at the moment though.
-
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. -
I see, apologies. I just fixed SSH access. You should be able to get through to it on port 6611.
-
What is the fingerprint for the SSH server?
-
root@d81ea330caf1:/# ssh-keyscan -p 6611 127.0.0.1 | ssh-keygen -lf - # 127.0.0.1:6611 SSH-2.0-APACHE-SSHD-2.9.2 # 127.0.0.1:6611 SSH-2.0-APACHE-SSHD-2.9.2 # 127.0.0.1:6611 SSH-2.0-APACHE-SSHD-2.9.2 # 127.0.0.1:6611 SSH-2.0-APACHE-SSHD-2.9.2 # 127.0.0.1:6611 SSH-2.0-APACHE-SSHD-2.9.2 4096 SHA256:aAC+3V5dUYFF4SStWNhjH0CN7hRLmSDmu/VlXoqR6fA [127.0.0.1]:6611 (RSA)
-
Previous Value Current Value Open
Closed
-
Ok, everything works now.
Type |
Task
|
Priority |
Major
|
Assignees |
Not assigned
|
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?