On Tue, December 3, 2013 14:59, Lee Hambley wrote: > There is no *encrypting* you should give SSH keys a shot. >
Hashing then. According to authconfig both the deploying and repository servers are using sha512. How does Capistrano send the password? This looks to me that whatever is happening to prevent the proper password from being recognized is happening inside Capistrano itself. ** [xnet241.hamilton.harte-lyne.ca :: out] Permission denied (publickey,password). ** [xnet241.hamilton.harte-lyne.ca :: out] fatal: The remote end hung up unexpectedly Yes, we can set up the keys on the git host but, as we spin up and remove virtual hosts for development and testing, making that an ongoing requirement is going to be a persistent irritation. Also, we did not have this problem originally so the issue is either some change to Ruby or some change to Capistrano. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:[email protected] Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/8344807e8ea4172eb6e5ffa2bc9c8e77.squirrel%40webmail.harte-lyne.ca. For more options, visit https://groups.google.com/groups/opt_out.
