Thought you might like to know -- the problem turns out to be user
error. I was watching the developer use the script, and I assumed
that when he entered the password for the target useid, that he had
configured the script to use the userid associated w/ the password.
As it turns out, he was taking the default which in this script is
${user.name} for which he does not have an account on the remote
system.
After he configured the correct userid for the ssh commands all worked well.
One more thing I'll have to add to the documentation for this script.
Michael
On 9/30/07, Michael Giroux <[EMAIL PROTECTED]> wrote:
> I personally do not use passphrase, but I'm not sure what the other
> developer is using on his system (the one having problems). I'll
> check on Monday.
>
> Thanks
>
> Michael
>
> On 9/29/07, Vihan Pandey <[EMAIL PROTECTED]> wrote:
> > > I'm using <scp> and <sshexec> tasks in a build script. These work
> > > well from my own PC, but when someone tries to run the script from a
> > > different computer, the script fails with an authentication error.
> > >
> > > I have been using <scp> and <sshexec> for so long, I no longer
> > > remember what I did to resolve this issue when I had it.
> > >
> > > We built the Shell.java example app that is distributed with JSch.jar.
> > > We were able to use Shell to connect to the target system, so it
> > > seems we have some ability to connect, but the ANT scripts continue to
> > > fail.
> >
> > Do you authenticate through password or keys alone or keys + passphrase?
> >
> > Regards,
> >
> > - vihan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
