SSH keys cab have passphrases, but I guess that's not the case here, since you didn't even know that it was. Can you share full logs?
Sent from my Nexus 5. On 13 Oct 2014 17:15, "Mel Riffe" <mri...@gmail.com> wrote: > I'm not sure I take your meaning, Lee. How would my passphrase force me to > enter a password when I thought the use of SSH keys alleviated the need for > passwords. > > As for more information: Sure - I'm just not sure which information is > needed. What should I be providing? > > --Mel > > > On Monday, October 13, 2014 6:11:31 AM UTC-4, Lee Hambley wrote: >> >> It may well be your ssh key's passphrase, it's impossible to say without >> more info. >> >> Lee Hambley >> -- >> http://lee.hambley.name/ >> +49 (0) 170 298 5667 >> >> On 10 October 2014 19:38, Mel Riffe <mri...@gmail.com> wrote: >> >>> First, I apologize if this has been asked and answered before. I'm >>> having difficulty forming the question so, of course, my search results are >>> varied and, generally, not useful. In fact I'm pretty sure my Topic title >>> is a bit misleading. :( >>> >>> Currently, for a client's project, we're using Cap 2.x. This is a >>> project I inherited and, as such, I can only speak to what I'm currently >>> seeing. However, the current deployment does not specify any user >>> information and relies on each developer being in my clients' 'deployers' >>> group and setting up SSH keys. >>> >>> My client has started a new Rails 4.x project and I thought, 'this would >>> be a good time to upgrade to Cap 3 and clean up the deployments' >>> >>> So, following along the Cold Start page (http://capistranorb.com/ >>> documentation/getting-started/cold-start/), I wrote the >>> 'check_write_permissions' task. I had defined my roles to use only the >>> server name. I was not expecting to be asked for a password, yet I was. >>> >>> Did I miss something? >>> >>> Thanks for any help provided! >>> >>> --Mel >>> >>> -- >>> 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 capistrano+...@googlegroups.com. >>> To view this discussion on the web, visit https://groups.google.com/d/ >>> msgid/capistrano/51d27d76-0156-458f-87ec-9397b100caf7%40googlegroups.com >>> <https://groups.google.com/d/msgid/capistrano/51d27d76-0156-458f-87ec-9397b100caf7%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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 capistrano+unsubscr...@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/capistrano/182b75b1-0e60-4763-8ea7-39be3ea78817%40googlegroups.com > <https://groups.google.com/d/msgid/capistrano/182b75b1-0e60-4763-8ea7-39be3ea78817%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 capistrano+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLWgb_bQU3PFb_9yjDTvtTvVfzt96Ne7qGBuAG7NFtMMfQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
