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

Login use one user and act as another user. #95881

Closed
allstable opened this issue Apr 22, 2020 · 2 comments
Closed

Login use one user and act as another user. #95881

allstable opened this issue Apr 22, 2020 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@allstable
Copy link

allstable commented Apr 22, 2020

Hello, here is an new request.
Image this situation:
Connect the remote host through a general user,which has only little privilege, and then elevate its privilege to a super user,let us say root. We need to do the work under the root user.
So, in VS Code, how can I make it? Becuase there is a situation where we can only use the general user to connect to the remote host.
Looking for the reply,thanks so much.
More info:
Login the remote host through a general user,but then need to switch to root(in the VS Code User Interface,not the VS Code Terminal),the files are down root home directory.Just like below:

图片

@allstable
Copy link
Author

Hello, here is an new request.
Image this situation:
Connect the remote host through a general user,which has only little privilege, and then elevate its privilege to a super user,let us say root. We need to do the work under the root user.
So, in VS Code, how can I make it? Becuase there is a situation where we can only use the general user to connect to the remote host.
Looking for the reply,thanks so much.
More info:
Login the remote host through a general user,but then need to switch to root(in the VS Code User Interface,not the VS Code Terminal),the files are down root home directory.Just like below:

图片

图片

@roblourens
Copy link
Member

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 25, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jun 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants