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.

Sign up for GitHub

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

Jump to bottom

SSH connection password rememberance feature along with storing list of connections #6541

Closed
krishlakshmanan opened this issue Jun 17, 2020 · 5 comments
Closed

SSH connection password rememberance feature along with storing list of connections #6541

krishlakshmanan opened this issue Jun 17, 2020 · 5 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@krishlakshmanan
Copy link

krishlakshmanan commented Jun 17, 2020 •
edited
Loading

After ssh connection to the machine is made, the user enter password has to be remembered with the user acknowledgement. Providing a list of ssh connection would make the user not to use the other ssh clients.
@krishlakshmanan krishlakshmanan added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 17, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 17, 2020
@harmjanwestra
Copy link

If you're using SSH on linux, these things can be arranged using ~/.ssh/config, private/public key pairs and an ssh-agent.

@fischerdouglas
Copy link

I would like to see som integration with Windows Password Vault, like iTerm2 does with MacOS Keyring.

@fischerdouglas
Copy link

I mentioned some suggestions for issues like this
#5880

#5916

@DHowett
Copy link
Member

DHowett commented Jun 17, 2020

Thanks for the request! For the reasons outlined in 5880 and a couple others, I'm gonna close this out. Please follow 5880 and 5916 (parent issue #4000) for more info.

/dup #5880

@ghost
Copy link

ghost commented Jun 17, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jun 17, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 17, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DHowett @harmjanwestra @krishlakshmanan @fischerdouglas