Have a look at http://stackoverflow.com/questions/23392763/aws-ssh-connection-error-permission-denied-publickey
> Le 14 juin 2016 à 10:29, Sverre Moe <[email protected]> a écrit : > > Got the following debug output. > > Wonder if it could have something to do with: > key_parse_private2: missing begin marker > However, the private key file has header "-----BEGIN RSA PRIVATE KEY-----" > and footer "-----END RSA PRIVATE KEY-----" > > debug2: key: private.key ((nil)), explicit > debug1: Authentications that can continue: publickey,keyboard-interactive > debug3: start over, passed a different list publickey,keyboard-interactive > debug3: preferred publickey,keyboard-interactive,password > debug3: authmethod_lookup publickey > debug3: remaining preferred: keyboard-interactive,password > debug3: authmethod_is_enabled publickey > debug1: Next authentication method: publickey > debug1: Trying private key: private.key > debug1: key_parse_private2: missing begin marker > debug1: read PEM private key done: type RSA > debug3: sign_and_send_pubkey: RSA > 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 [MD5] > debug2: we sent a publickey packet, wait for reply > debug1: Authentications that can continue: publickey,keyboard-interactive > debug2: we did not send a packet, disable method > debug3: authmethod_lookup keyboard-interactive > debug3: remaining preferred: password > debug3: authmethod_is_enabled keyboard-interactive > debug1: Next authentication method: keyboard-interactive > debug2: userauth_kbdint > debug2: we sent a keyboard-interactive packet, wait for reply > debug2: input_userauth_info_req > debug2: input_userauth_info_req: num_prompts 1 > > tirsdag 14. juni 2016 09.47.08 UTC+2 skrev Thomas Zoratto følgende: >> >> Ok, then try to ssh manually with full verbose mode (-vvv) >> >>> Le 14 juin 2016 à 08:54, Sverre Moe <[email protected]> a écrit : >>> >>> The private key is actually not password protected. I chose empty password >>> when I generated the private key on the server. >>> >>> tirsdag 14. juni 2016 08.41.17 UTC+2 skrev Thomas Zoratto følgende: >>>> >>>> Your private keys seems to be protected by a passphrase. As you are not in >>>> an interactive shell there is no tty so it fails when trying to ask for >>>> passphrase. >>>> >>>>> Le 14 juin 2016 à 08:20, Sverre Moe <[email protected]> a écrit : >>>>> >>>>> It looks like it is trying the private key credentials from Jenkins, but >>>>> fails. When it fails it tries the public key for the user, then finally >>>>> trying password which it cannot get. >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: Next authentication method: publickey >>>>> debug1: Offering RSA public key: build (company-server) >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: Offering RSA public key: /home/build/.ssh/id_rsa >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: Trying private key: /home/build/.ssh/id_dsa >>>>> debug1: Trying private key: /home/build/.ssh/id_ecdsa >>>>> debug1: Next authentication method: keyboard-interactive >>>>> debug1: read_passphrase: can't open /dev/tty: No such device or address >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: read_passphrase: can't open /dev/tty: No such device or address >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: read_passphrase: can't open /dev/tty: No such device or address >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: No more authentication methods to try. >>>>> Permission denied (publickey,keyboard-interactive). >>>>> >>>>> I don't think the problem is with either Jenkins og Agent SSH Plugin as I >>>>> am getting almost the same problem manually executing ssh with the >>>>> private key. >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: Next authentication method: publickey >>>>> debug1: Trying private key: private.key >>>>> debug1: read PEM private key done: type RSA >>>>> debug1: Authentications that can continue: publickey,keyboard-interactive >>>>> debug1: Next authentication method: keyboard-interactive >>>>> Password: >>>>> >>>>> mandag 13. juni 2016 19.21.10 UTC+2 skrev Thomas Zoratto følgende: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Try to ssh in verbose mode and you'll know what's happening. >>>>>> >>>>>> ssh -v ... >>>>>> >>>>>> (The more v you put, the more verbose it will be) >>>>>> >>>>>>> Le 13 juin 2016 à 15:21, Sverre Moe <[email protected]> a écrit : >>>>>>> >>>>>>> I have already added the host to ~/.ssh/known_hosts, so using >>>>>>> StrictHostKeyChecking=no is no longer necessary. >>>>>>> What I am experiencing now is authentication problem. It does not use >>>>>>> the credentials with the ssh connection. Thus I receive Permission >>>>>>> denied (publickey,keyboard-interactive). >>>>>>> >>>>>>> My credentials contain the private key for the username I use in the >>>>>>> ssh command. >>>>>>> >>>>>>> Wonder if the problem lies not with sshagent, but elsewhere. >>>>>>> I have tried the following command manually with the same private-key >>>>>>> stored in Jenkins for this user and it still asks for password. >>>>>>> ssh -i private.key [email protected] >>>>>>> Password: >>>>>>> Password: >>>>>>> Password: >>>>>>> Permission denied (publickey,keyboard-interactive). >>>>>>> >>>>>>> However still do sshagent supply the private key when executing ssh? >>>>>>> >>>>>>> >>>>>>> mandag 13. juni 2016 14.36.38 UTC+2 skrev Baptiste Mathus følgende: >>>>>>>> >>>>>>>> Indeed in my case I had disabled host key checking. >>>>>>>> >>>>>>>> What works for me is: >>>>>>>> >>>>>>>> sshagent(['some-id']) { >>>>>>>> >>>>>>>> sh """ >>>>>>>> ssh -o StrictHostKeyChecking=no marmotte@marmotte "docker >>>>>>>> create -v /var/jenkins_home --name ze-data jenkins:1.642.1 || echo >>>>>>>> 'data container already existing?' " >>>>>>>> .... >>>>>>>> """ >>>>>>>> } >>>>>>>> >>>>>>>> 2016-06-13 9:53 GMT+00:00 Sverre Moe <[email protected]>: >>>>>>>>> Am i missing something in my script content? >>>>>>>>> sshagent(['repository']) { >>>>>>>>> sh 'ssh -Xf [email protected] ls -l /home/build/ ' >>>>>>>>> } >>>>>>>>> >>>>>>>>> When executing ssh within sshagent I am getting >>>>>>>>> Permission denied (publickey,keyboard-interactive). >>>>>>>>> >>>>>>>>> The credential repository has the private key for the user build. >>>>>>>>> >>>>>>>>> torsdag 2. juni 2016 16.10.16 UTC+2 skrev Sverre Moe følgende: >>>>>>>>>> >>>>>>>>>> I need to transfer some files to a server. >>>>>>>>>> Have followed the suggestion mention in >>>>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-27963 >>>>>>>>>> Tried sshagent with both scp and rsync. Neither works. >>>>>>>>>> >>>>>>>>>> I have created a Credential for this server in Jenkins. >>>>>>>>>> >>>>>>>>>> Using rsync >>>>>>>>>> sshagent(['repository']) { >>>>>>>>>> sh "rsync -av *.rpm >>>>>>>>>> [email protected]:/srv/www/htdocs/staging_rpms/" >>>>>>>>>> } >>>>>>>>>> >>>>>>>>>> [ssh-agent] Using credentials build (repohost) >>>>>>>>>> [ssh-agent] Looking for ssh-agent implementation... >>>>>>>>>> [ssh-agent] Java/JNR ssh-agent >>>>>>>>>> [ssh-agent] Started. >>>>>>>>>> [Pipeline] { >>>>>>>>>> [Pipeline] sh >>>>>>>>>> [master] Running shell script >>>>>>>>>> + rsync -av *.rpm >>>>>>>>>> [email protected]:/srv/www/htdocs/staging_rpms >>>>>>>>>> Host key verification failed. >>>>>>>>>> rsync: connection unexpectedly closed (0 bytes received so far) >>>>>>>>>> [sender] >>>>>>>>>> rsync error: error in rsync protocol data stream (code 12) at >>>>>>>>>> io.c(641) [sender=3.0.4] >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Using scp >>>>>>>>>> sshagent(['repository']) { >>>>>>>>>> sh "scp *.rpm >>>>>>>>>> [email protected]:/srv/www/htdocs/staging_rpms/" >>>>>>>>>> } >>>>>>>>>> >>>>>>>>>> [ssh-agent] Using credentials build (repohost) >>>>>>>>>> [ssh-agent] Looking for ssh-agent implementation... >>>>>>>>>> [ssh-agent] Java/JNR ssh-agent >>>>>>>>>> [ssh-agent] Started. >>>>>>>>>> [Pipeline] { >>>>>>>>>> [Pipeline] sh >>>>>>>>>> [master] Running shell script >>>>>>>>>> + scp *.rpm [email protected]:/srv/www/htdocs/staging_rpms/ >>>>>>>>>> Host key verification failed. >>>>>>>>>> lost connection >>>>>>>>>> >>>>>>>>>> Problem because of this: >>>>>>>>>> The authenticity of host 'server.company.com (192.24.17.73)' can't >>>>>>>>>> be established. >>>>>>>>>> ECDSA key fingerprint is >>>>>>>>>> 00:00:00:00:00:00:00:bc:cc:51:3f:39:f8:06:df:18 [MD5]. >>>>>>>>>> Are you sure you want to continue connecting (yes/no)? yes >>>>>>>>>> Warning: Permanently added 'server.company.com' (ECDSA) to the list >>>>>>>>>> of known hosts. >>>>>>>>>> >>>>>>>>>> Fixing this first "manually" and continued. >>>>>>>>>> >>>>>>>>>> Using rsync >>>>>>>>>> [ssh-agent] Using credentials build (repohost) >>>>>>>>>> [ssh-agent] Looking for ssh-agent implementation... >>>>>>>>>> [ssh-agent] Java/JNR ssh-agent >>>>>>>>>> [ssh-agent] Started. >>>>>>>>>> [Pipeline] { >>>>>>>>>> [Pipeline] sh >>>>>>>>>> [master] Running shell script >>>>>>>>>> + rsync -av *.rpm >>>>>>>>>> [email protected]:/srv/www/htdocs/staging_rpms/ >>>>>>>>>> Permission denied (publickey,keyboard-interactive). >>>>>>>>>> rsync: connection unexpectedly closed (0 bytes received so far) >>>>>>>>>> [sender] >>>>>>>>>> rsync error: error in rsync protocol data stream (code 12) at >>>>>>>>>> io.c(641) [sender=3.0.4] >>>>>>>>>> >>>>>>>>>> Using scp >>>>>>>>>> [ssh-agent] Using credentials build (repohost) >>>>>>>>>> [ssh-agent] Looking for ssh-agent implementation... >>>>>>>>>> [ssh-agent] Java/JNR ssh-agent >>>>>>>>>> [ssh-agent] Started. >>>>>>>>>> [Pipeline] { >>>>>>>>>> [Pipeline] sh >>>>>>>>>> [master] Running shell script >>>>>>>>>> + scp *.rpm [email protected]:/srv/www/htdocs/staging_rpms/ >>>>>>>>>> Permission denied (publickey,keyboard-interactive). >>>>>>>>>> lost connection >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Jenkins Users" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/db0ba327-53d3-46f4-a09d-feeb3d539104%40googlegroups.com. >>>>>>>>> >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Jenkins Users" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>>> an email to [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/434015fa-5aa1-4d03-ac0a-93eada305d53%40googlegroups.com. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send an >>>>> email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/0d840fa3-bbb8-4933-80bf-d35c26451194%40googlegroups.com. >>>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/080fb889-6a54-45a6-a557-e0f24a39181e%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/b6a9939d-475a-448e-a462-d259786ee852%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7B1A3681-8140-43FA-BC35-E1DD67445D41%40gmail.com. For more options, visit https://groups.google.com/d/optout.
