New sample hello world C# no longer can debug

when I create a new “hello world” c# (.net) doesn’t work in debug anymore.
and here is the error

Starting: "ssh" -T -p 32768 -i c:\ToradexTestApp\cstest\appconfig_0\id_rsa -o StrictHostKeyChecking=no -o "UserKnownHostsFile /dev/null" torizon@ "/vsdbg/vsdbg --interpreter=vscode"
Error from pipe program 'ssh': Warning: Permanently added '[]:32768' (ECDSA) to the list of known hosts.
Error from pipe program 'ssh': @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Error from pipe program 'ssh': @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
Error from pipe program 'ssh': @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Error from pipe program 'ssh': Permissions for 'c:\\ToradexTestApp\\cstest\\appconfig_0\\id_rsa' are too open.
Error from pipe program 'ssh': It is required that your private key files are NOT accessible by others.
Error from pipe program 'ssh': This private key will be ignored.
Error from pipe program 'ssh': Load key "c:\\ToradexTestApp\\cstest\\appconfig_0\\id_rsa": bad permissions

but the old hello world program that I create 2 weeks still can work.
I have no idea what this means and how to fix it. I try many time, recreating new one, rebooting, rebuilding, deleting work folder, stoping the container and retry, never work.

I figured out. you need to remove all other user except yourself for the file id_rsa in the security tab.
The hello world sample I created 2 weeks ago only have myself as the user in the security tab.
the recent one create user for all users, admin, authorized user, etc… not sure why the change.

Interesting, I assume you’re on a Windows machine correct? The new project may have been created under a different user/strange circumstances. In any case glad to hear you were able to resolve the issue yourself. Please let me know if you’re able to reproduce this in the future. The information would be helpful for future reference.

Best Regards,

it is currently always creating project with the id_rsa file with all users access.
I tried it many times.

I’m unable to reproduce this on my own Windows machine. While the extension does generate the key files, it doesn’t do anything in terms of the permissions of those files. The files when they’re generated might be inheriting their permissions from some configuration or something similar.

Perhaps try the suggestions found in this thread here: How to secure SSH Private key on Windows 10 - Super User

Best Regards,