Maximilian Haupt

It looks like it is working as expected when using a key of type `ed25519`. I created a branch in the other repo to show the client code changes: https://github.com/0x7f/ssh-authentication-bug/pull/1...

@mscdex as far as o understand the latest comment in the other issue (https://github.com/golang/go/issues/66438#issuecomment-2016458723) the ssh2 library is doing something non-standard which is handled by OpenSSL client, but not by...

I did some more testing. I can confirm that my issue is fixed when using the proposed patch for the golang SSH client which accepts the algo returned by the...

@mscdex let me know if I can help in any way to get this fixed.

Hey, sorry for the late response. We had stability issues with our backend the last days. Everything should be working fine again since today morning. We are working on fixes...

Hi @zwass the loophole backend is not doing anything with the encrypted https connection. So this can not block WebSocket usage. But it might be that the CLI is not...

Hey, sorry for the inconvenience. The backend system was stuck. Restarted it and it works again. We did not find time to fix this yet, as we are busy with...

Can you please try opening the tunnel on another device? Your phone for example. Maybe your computer has a strange configuration in terms of SSL certificates. I did not run...

Yes, the retry would improve the API here as well.

Hm, you say he is retrying forever. But why is he not catching up again when the whole cluster was down and then restarted again? Can you reproduce this?