Jeremy, caching the key (which is the default behaviour of the supported key agents) is indeed a requirement; whilst this may not suit your situation perfectly, it's the only way this can work. I will bear in mind to create successful connections first, that people might use multiple keys (also a problem...for which we don't have a solution) - this would solve you use-case, but regrettably isn't an easy fix.
Sorry I can't be more help, and you are right - calling a key agent defective is a little harsh; however the only practical use of the agent is to cache an unlocked key for easier access, which implies that it should store the key without re-prompting, any overview at the purpose of key agents should confirm this, without that - they aren't serving any purpose. (maybe your agent isn't even supported by Capistrano) Earlier guides for Capistrano insisted that you use `ssh-agent add` (or your platform's equivalent) to add the relevant keys for your host to the agent prior to attempting a deploy. - HTH, Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
