VSCode SSH on v0.60.0

General Discussion
1

Hey there everyone! :waving_hand:

The new v0.60.0 just dropped a few days ago and it seems there were a lot of changes regarding ssh.

Now of course I updated straight away, but now am experiencing some issues:

I am currently using VSCode Remote SSH for connecting to my Netbird peers (worked really good!) up until the new update I was able to connect to my peers like always.
After updating my peers to the newest version and connecting to them I noticed that one of the two requested a OIDC authentication (cool, but not what I want), so I added --disable-ssh-auth, but that also didn’t help then it seemed like there was no authentication whatsoever (I guess that’s why it is called disable..ssh..auth, but to my understanding only jwt auth should be disabled with that), I can just ssh into the peer without any password.
Using the terminal was working (great!), but then when trying out VSCode it couldn’t connect, I am not sure why…

The first peer seems to still be working with password-only and it also didn’t change its ssh key, but the second peer (the one where VSCode is failing) did (… change its key).

Now my question is:

  1. How do I change it back to requesting a Password each time?

    AND

  2. Why did the first peer not change its key and still works with VSCode?

Context:

  • Yes, I have enabled ssh vai UI and cmdline
  • Yes, both the client and peer 1+2 are on v0.60.2
  • Yes, I have restarted both of my peers
  • Yes, I can ping both peers, they are connected
  • Yes, I have setup an ACL Rule

Logs:

local-server-1> Spawned ssh, pid=335993
OpenSSH_9.6p1 Ubuntu-3ubuntu13.14, OpenSSL 3.0.13 30 Jan 2024
debug1: Server host key: ssh-ed25519 SHA256:REDACTED
Authenticated to peer-2.domain.com ([PEER2_IP]:22) using "none".
no command specified and Pty not requested
Transferred: sent 1904, received 1384 bytes, in 0.0 seconds
Bytes per second: sent 152035.9, received 110513.5
local-server-1> ssh child died, shutting down

Thanks in advance!

2

Did you setup a ACL for the SSH connection?

  • Machine Identity (--disable-ssh-auth): When SSH auth is disabled, SSH access is governed by NetBird network ACLs (machine-level access) rather than per-user JWT identity.

Either port 22022 or 22. Just for debugging pourpuses.

3

Yes, sorry, I have an Allow All ACL Rule in place.

EDIT: also added a rule for port 22 specifically, but still not working.

4

SSH is working it is just that it isn’t asking for a password and that VSCode is exiting out due to some error.

Peer 1 is accessible like always even with VSCode eventho it is in the same groups, etc…

5

It seems that on Peer 1 ssh server is disabled. Which then makes sense why it was still working with VSCode.

Disabling ssh on Peer 2 via the UI worked! But this is technically just a workaround…