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

Better SSH authentication management #2

Closed
rsaikali opened this issue Aug 22, 2012 · 4 comments
Closed

Better SSH authentication management #2

rsaikali opened this issue Aug 22, 2012 · 4 comments

Comments

@rsaikali
Copy link
Owner

To avoid storing passwords in database, SSH authentication should be managed differently.

Use of SSH keyfiles should be studied.

@rsaikali
Copy link
Owner Author

v0.0.5 enhancement : use fabric local() command if server ip is detected as 127.0.0.1

Not a big deal, but better than nothing : faster execution (no SSH) no need for username/password.

@mbi
Copy link
Contributor

mbi commented Sep 12, 2012

It seems to me this is could simply be covered by documentation, i.e.

  • leave the password field empty
  • if needed, create a ssh key (ssh-keygen)
  • copy the key to every server being monitored (ssh-copy-id)

This already works flawlessly.

@rsaikali
Copy link
Owner Author

That's what I wanted to try (need time !!)
I knew this was the default Fabric behaviour, but I wondered if it worked in a Django environment (don't know why it shouldn't).

Thanks for testing that...

"This already works flawlessly."
So I close this ticket...

@rsaikali
Copy link
Owner Author

"It seems to me this is could simply be covered by documentation"

Correct ! Need to review the docs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants