-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unprotected private key file #6615
Comments
Are you trying to access Gitpod workspace from VS Code Desktop? |
@akosyakov hi! Yes, exactly |
@lucas-labs Thank you for writing a detailed bug report :) Unfortunately I haven't been able to reproduce the bug, so if it's okay with you I would like to ask a few more questions. Some context as to why you are getting the error: This error happens because, the ssh keys are supposed to be in a path that is accessible only to the user. But if the private key is in the I did the following steps when attempting reproduce the bug:
Looking at the logs of VSCode RemoteSSH extension, it looks like for me Gitpod automatically created the SSH key pairs and wrote it to my TEMP directory Digging into git commit history, it looks like due to this commit, Gitpod now automatically produces SSH keypair per-workspace and store them in the TEMP directory of the operating system, contrary to what is mentioned in the Introductory blog of the Local Companion.
Looks like the blog is slightly outdated, (Note to self: Update the docs?) Sorry, for the detour, getting back to it. The automatic generation of ssh key-pair per workspace is now handled via func generateSSHKeys(instanceID string) (privateKeyFN string, publicKey string, err error) {
privateKeyFN = filepath.Join(os.TempDir(), fmt.Sprintf("gitpod_%s_id_rsa", instanceID)) As you can see above, we use
And ideally the Temporary path for Windows is stored at:
And this is where the Gitpod stores my ssh keys as well. QuestionsBut oddly, the path from where the gitpod is trying to read the ssh keys in your case is from
The above files should ideally be in the This would really help me pinpoint what is going wrong and fix it ^^ P.S: Apologies for such a long message ^^' |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@lucas-labs I appear to be having this issue as well |
Noting this issue will likely be resolved with new SSH access method: #8513 |
Just hit this today. Went to my repo Looking at previous remarks here, I note that I have overridden the user and system env vars for 🡆🡆UPDATE: On setting
VSCode output window:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Does this issue occur when all extensions are disabled?: Yes
I'm seeing the following error when trying to open with VSCode
The problem is with the permissions of the file gitpod_01460b4a-fe2a-4d71-8fee-f0d065765c8a_id_rsa. As the error says, permissions are too open:
(sorry for the spanish texts in the screenshot)
Changing the permission of the file so that only my user can access to it works, but I have to do that every time a new rsa file is being created, which is inconvenient.
Is there any other, more permanent, solution?
Thanks!!
The text was updated successfully, but these errors were encountered: