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

Support autenticate with private key without have too make an Putty Session #1190

Open
marcomsousa opened this issue Nov 15, 2018 · 1 comment
Labels
Enhancement A new feature or improvement to an existing feature.

Comments

@marcomsousa
Copy link
Contributor

marcomsousa commented Nov 15, 2018

mRemoteNG should support that we put the URI file to the private key directly in the conexions tab.

Expected Behavior

mRemoteNG should support that we put the URI to the private key directly in the connections tab.
It's a very common and more secury authentication in Linux.

Current Behavior

  1. Create a new conexion
  2. Change name, protocol, and username
  3. Open putty, configure pointing to private key, save with the same name before
  4. Change session in mRemoteNG to the same same has before.
  5. Save backup (don't have the part in putty)

Possible Solution

mRemoteNG should support that we put the URI file to the private key directly in the conexions tab.

Context

I have a lot of VM and we authenticate with private keys, not passwords. (SSH v2)
So, we have more than 200 VMs and we need to have almost 200 putty sessions.

Your Environment

  • Windows
  • Remote -> Linux ssh with private keys
@kmscode kmscode added the Enhancement A new feature or improvement to an existing feature. label Dec 10, 2018
@penguinairlines
Copy link

If we could, while we're at it, make this suggested field with variable support, then we could also use that field for external tools. I opened up a dedicated issue #2046 about this before finding this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A new feature or improvement to an existing feature.
Projects
None yet
Development

No branches or pull requests

3 participants