Well, I tried it with all user.
Anderson, Rob (Global Trade) schrieb:
Are you logging in as root?
-Rob A
-----Original Message-----
From: Peter Neu [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 08, 2004 6:12 AM
To: Ant Users List
Subject: Re: sshexec Authentication Problem with SuSE 9.1
Hello Rob,
the error output is at the end of the message. The way I read it
JSCH is not supported by sshd.
The debug information from sshexec task is the same.
Atsuhiko suggested to enable "PAMAuthenticationViaKbdInt" which is
decaprecated
in OpenSSH.3.8.
Regards,
Peter
------ Debug--Output-----------------------------------------------
linux:~ # sshd -d -p 23
debug1: sshd version OpenSSH_3.8p1
debug1: private host key: #0 type 0 RSA1
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 23 on ::.
Server listening on :: port 23.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from ::ffff:192.168.2.101 port 1132
debug1: Client protocol version 2.0; client software version
JSCH-0.1.18
debug1: no match: JSCH-0.1.18
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-1.99-OpenSSH_3.8p1
debug1: permanently_set_uid: 71/65
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server 3des-cbc hmac-md5 none
debug1: kex: server->client 3des-cbc hmac-md5 none
debug1: expecting SSH2_MSG_KEXDH_INIT
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user root service ssh-connection
method none
debug1: attempt 0 failures 0
Failed none for root from ::ffff:192.168.2.101 port 1132 ssh2
debug1: PAM: initializing for "root"
Received disconnect from ::ffff:192.168.2.101: 3:
com.jcraft.jsch.JSchException:
Auth fail
debug1: do_cleanup
debug1: PAM: cleanup
debug1: PAM: setting PAM_RHOST to "192.168.2.101"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: do_cleanup
debug1: PAM: cleanup
Since you get the same error when you use wrong login and
pass, it would appear that Authentication is failing, even
when you use the right login and pass.
You might try to run sshd on the server in verbose mode on a
different port and see what the output is when you try to
connect using the sshexec task.
Start sshd as root with the following command line...
sshd -v -p 1022
Then add the port number to your ant build file and try to
run it. There is also an undocumented verbose attribute to
the sshexec task that you might want to set to true.
<sshexec host="192.168.2.5"
trust="true"
username="tom"
password="darksecret"
command="mkdir simple"
port="1022"
verbose="true"/>
Capture the output from sshd and send it. Also send the
output from the ant build with verbose="true", if it is
different than what you sent before.
-Rob Anderson
-----Original Message-----
From: Peter Neu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 11:48 AM
To: Ant Users List
Subject: Re: sshexec Authentication Problem with SuSE 9.1
Hello Rob,
I only got SuSE 9.1 client/servers in my network. I works on
neither of
them.
I got Jsch 0.1.18. I tried wrong logins which yield to the
same result.
I really
got no idea what could be wrong.
Regards,
Peter
The error is "Auth fail". Perhaps the username or password
is incorrect? Try using a username or password that you know
is incorrect and see if you get the same error. Also, what
version of Jsch are you using? Can you connect to any other
hosts with the sshexec task?
-Rob Anderson
-----Original Message-----
From: Peter Neu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 4:49 AM
To: Ant Users List
Subject: Re: sshexec Authentication Problem with SuSE 9.1
Hello Rob,
the server has OpenSSH 3.8p1-33 installed. The exception
looks like this
BUILD FAILED
C:\Antworker II\Ant-Trial\build.xml:11:
com.jcraft.jsch.JSchException:
Auth fail
at
org.apache.tools.ant.taskdefs.optional.ssh.SSHExec.execute(SSH
Exec.java:211)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement
.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:673)
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
Caused by: com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at
org.apache.tools.ant.taskdefs.optional.ssh.SSHBase.openSession
(SSHBase.java:1
at
org.apache.tools.ant.taskdefs.optional.ssh.SSHExec.execute(SSH
Exec.java:143)
... 10 more
--- Nested Exception ---
com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at
org.apache.tools.ant.taskdefs.optional.ssh.SSHBase.openSession
(SSHBase.java:1
at
org.apache.tools.ant.taskdefs.optional.ssh.SSHExec.execute(SSH
Exec.java:143)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement
.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:673)
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
I hope this is enough input. Authentication is OK works
with clients
like putty.
Regards,
Peter
Anderson, Rob (Global Trade) schrieb:
Jsch is an implementation of SSH2. It does not support SSH1.
What is the error message you are getting? What
implementation of SSH2 are you using on the server? OpenSSH?
-Rob Anderson
-----Original Message-----
From: Peter Neu [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 04, 2004 2:16 AM
To: Ant Users List
Subject: sshexec Authentication Problem with SuSE 9.1
Hello ,
I'm trying to start tomcat on a remote machine.
<sshexec host="192.168.2.5"
trust="true"
username="tom"
password="darksecret"
command="mkdir simple"/>
The problem is the remote machine only supports SSH 2.
It seems that the implementation in *JSch is not ready for *
*this. Has anyone an idea what to do in this case? *
**
*I had the same problem with an old version of putty until*
*I upgraded it to a newer version.*
**
*Regards,*
**
*Peter*
**
------------------------------------------------------------
---------
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]
------------------------------------------------------------
---------
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]
------------------------------------------------------------
---------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
