microsoft / microsoft/vscode-remote-release
[Remote-SSH Bug]: Session keyring corrupted by remote-ssh, breaks azcopy
Open
@roblourens is already working on this.
Since Sep 3, 2023.
feature-request
ssh
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing issues
Required Troubleshooting Steps
- I have followed these troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting
Connect Locally
It connects successfully
->
No response
Expected Behavior
When using Remote-SSH I cannot use tools like azcopy which depend on having a keyring session in place. I can work around by using keyctl to create a new session, but this doesn't work when running powershell scripts.
Steps To Reproduce
I'm connecting to a RHEL 7 machine. All default settings. When I use ssh outside of VS Code I have no problems.
Outside of VS Code:
$ keyctl show
Session Keyring
1029758406 --alswrv 1000 1000 keyring: _ses
182756408 --alswrv 1000 65534 \_ keyring: _uid.1000
In VS Code:
$ keyctl show
Session Keyring
Unable to dump key: Key has been revoked
Remote-SSH Log
Remote-SSH Log
[08:02:36.160] Log Level: 2
[08:02:36.191] VS Code version: 1.81.1
[08:02:36.191] Remote-SSH version: remote-ssh@0.105.2023080715
[08:02:36.191] win32 x64
I removed the ConfigFileWatcher entries at the end of the log as they show details I'd rather not share and don't pertain to this issue.
Anything else?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.