The passphrase checking and prompting is actually all handled by Net::SSH, and not Capistrano, which is why cap doesn't cache the passphrase. I'd strongly recommend using an ssh agent, rather than hard-coding your key paths. However, what you've reported is a bug, and when I get a chance I'll look into it, but I have to admit that it's not very high on my list of priorities right now (TONS of other things pending). If anyone else is passionate about seeing this bug fixed, a patch would be the fastest road to a fix.
- Jamis On Jun 6, 2007, at 9:42 AM, Mat Schaffer wrote: > > I have two servers I'm referencing in my Capfile. Both of which are > set up to use my rsa key in ~/.ssh. SSH is configured fine, I can > get in. Capistrano even recognizes this and automatically prompts me > for the passphrase to the key. No issues there. > > When attempting to connected to the second server it appears to > hang. If I hit enter, I get a second passphrase prompt. It looks > like Capistrano is not doing anything to cache the passphrase for the > key. This might be intentional because I could use ssh-agent to do > this. > > I think the real issue is that the invisible second prompt (although > automatic use of ssh-agent to cache the passphrase would be cool > too). I'm guessing the pipe isn't quite working how it's supposed to. > > This is on capistrano 1.99.1, Mac 10.4, MacPorts ruby 1.8.6 > > Sorry if this is redundant report, I couldn't find anything in google > groups about it. The closest thing I found in rails trac was #2722. > Is there a new Trac somewhere? > > Thanks for the great work so far! > -Mat > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
