Thanks for the replies.

I'm using svn+ssh:// with the same username as my local development
user and my server account. Even with authorized_keys set up
correctly, I get the same ssh-askpass errors.

What's weird is that if I run cap deploy from the server, it works. If
I deploy from another development machine, I get these errors even
though I'm properly authenticated.

I'll keep poking around, thanks again for the advice.

On Nov 16, 4:21 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Look in deploy.rb and check which ':user' is being used. Be sure it
> matches the same user associated with the key on your server (located
> in /username/.ssh).
>
> http://www.webficient.com/2007/11/mac-and-ssh-keys.html
>
> On Nov 12, 1:03 pm, Scott <[EMAIL PROTECTED]> wrote:
>
> > After updating to Capistrano 2.1, I started getting this while using
> > cap deploy:update and svn+ssh:
>
> > ---
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] Permission denied, please try again.
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] Permission denied, please try again.
> >  ** [err] ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or
> > directory
> >  ** [err] Received disconnect from <server_ip>: 2: Too many
> > authentication failures for <user_name>
> > ---
>
> > I know for a fact that Mac OS 10.4 doesn't have /usr/libexec/ssh-
> > askpass...
>
> > Is Capistrano doing this, or is something else going on?
>
> > TIA
>
> > Scott
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to