Skip to content
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

Creating an SSH key/pair for host with invalid characters breaks Che for that user #14912

Closed
andy316x opened this issue Oct 17, 2019 · 3 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@andy316x
Copy link

Platform
Openshift v3.11
Che 7.3.0-SNAPSHOT

Steps to reproduce
Open a workspace
Run the command “SSH: Generate key pair for particular host”
Enter a host with an invalid character - for example a space a forward slash
Close the workspace and try and reopen it
Openshift throws an error saying that the secret being generated is invalid

This is a real issue as the user can no longer open any workspace, meaning they can’t even rectify the problem themselves, rendering Che completely unusable for the affected user, with no means to recover.

I was able to resolve the issue for the affected user by removing the invalid key pair from the Postgres DB.

I think what needs to happen is for the host to be validated by the generate key pair command before allowing it to be created - this validation process should at least only permit acceptable values in an Openshift secret name. Or maybe the host value that is used to create the secret name needs to be sanitised.

@andy316x andy316x added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 17, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 17, 2019
@tsmaeder tsmaeder added severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. team/ide severity/P1 Has a major impact to usage or development of the system. and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 18, 2019
@tsmaeder
Copy link
Contributor

I am not assigning "blocker" because I don't expect many users to encounter it, but once it happens, it sounds really bad.

@vparfonov vparfonov added this to the Backlog - IDE 1 milestone Oct 18, 2019
@vparfonov
Copy link
Contributor

we have PR for this need to test it again #14243

@vparfonov vparfonov modified the milestones: Backlog - IDE 1, 7.4.0 Oct 23, 2019
@vinokurig
Copy link
Contributor

Since new SSH keys name validation has been applied: eclipse-che/che-theia#444 it could be reproduced only by creating a key via API.

@vparfonov vparfonov modified the milestones: 7.4.0, Backlog - IDE 1 Nov 6, 2019
@vparfonov vparfonov modified the milestones: Backlog - IDE 1, 7.5.0 Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants