On Tue, Mar 14, 2023 at 3:39 PM Kari Klein <
kkl...@rumission.com> wrote:
>
>
>
> On Tue, Mar 14, 2023 at 2:15 PM Matthias Sohn <
matthi...@gmail.com> wrote:
>>
>> On Tue, Mar 14, 2023 at 9:08 PM Kari Klein <
kkl...@rumission.com> wrote:
>>>
>>> So I tried that by removing the line "advertisedAddress = *:22" in the config and opening up that port firewall settings via tcp and udp for all incoming IP addresses on my vm and also running "sudo ufw allow 29418/tcp" and "sudo ufw allow 29418/udp" on the vm, but that connection times out when I run this:
>>
>>
>> Please avoid top posting on this list, use interleaved posting instead.
>> See
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
>>
>> Try if you can connect using this command
>>
>> ssh -v -p 29418 username@host
>>
>> -v should give you some details about what's going wrong
>
>
> Thanks for the tip on interleaving.
>
> I finally got it working. I needed to do a few things. My port firewall settings weren't quite right on the VM, then I needed to use ED25519 for the encryption for my key, and then I had to use the command with my username: git clone ssh://
kkl...@gerrit.rumission.com:29418/test-vs.git test-vs
>
If your previous key was an RSA key then it is possible you ran into
issues with the new OpenSSH clients disallowing RSA + SHA1 by default
and older Gerrit servers not understanding how to negotiate RSA + SHA2
with these clients. This was fixed in Gerrit 3.6 and newer and
eventually backported to Gerrit 3.5. This means that an up to date
Gerrit 3.5 or newer should work with RSA keys and new OpenSSH clients.
That said, ED25519 keys should work fine. I'm mostly calling this out
should anyone else run into similar problems.