Better SSH authentication management #2

rsaikali opened this Issue Aug 22, 2012 · 4 comments


None yet

2 participants


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

Use of SSH keyfiles should be studied.


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

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


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.


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 rsaikali closed this Sep 12, 2012

"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