[JIRA] [ssh-agent-plugin] (JENKINS-18897) ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'
Title: Message Title Stan Towianski commented on JENKINS-18897 Re: ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath' Hi. You can actually get it to work with a passphrase on your private key. see: https://issues.jenkins-ci.org/browse/JENKINS-32120 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-24658) ssh-agent fails with "JCE cannot authenticate the provider BC" on slave
Title: Message Title Stan Towianski commented on JENKINS-24658 Re: ssh-agent fails with "JCE cannot authenticate the provider BC" on slave Hi. You can actually get it to work with a passphrase on your private key. see: https://issues.jenkins-ci.org/browse/JENKINS-32120 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" [ssh-agent] Using credentials myUser (with private key and passphrase) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Unable to read key: exception using cipher - please check password and data. org.bouncycastle.openssl.EncryptionException: exception using cipher - please check password and data. at org.bouncycastle.openssl.PEMUtilities.crypt(Unknown Source) at org.bouncycastle.openssl.PEMUtilities.crypt(Unknown Source) at org.bouncycastle.openssl.PEMReader$KeyPairParser.readKeyPair(Unknown Source) at org.bouncycastle.openssl.PEMReader$RSAKeyPairParser.parseObject(Unknown Source) at org.bouncycastle.openssl.PEMReader.readObject(Unknown Source) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.addIdentity(JNRRemoteAgent.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.SecurityException: JCE cannot authenticate the provider BC at javax.crypto.Cipher.getInstance(Cipher.java:657) ... 21 more Caused by: java.util.jar.JarException: Class is on the bootclasspath These are are related as far as I can tell. A teammate figured out Bouncy Castle problem has to be done on a build slave if you are using those. I'm not sure if it needs to be done on the Jenkins master too, but I did it there first already. I think java 6 does not work with newer Jenkins? I did not test fix with java 7. I used Java 8 add these 4 jar files here: /…./java/jdk/jdk-1.8u66/jre/lib/ext rw-r r - 1 root root 2070477 Feb 25 16:46 bcprov-ext-jdk15on-147.jar rw-r r - 1 root root 1997327 Feb 25 16:46 bcprov-jdk15on-147.jar /…./java/jdk/jdk-1.8u66/jre/lib/security rw-r r - 1 ro
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" so, it looks like what I did to get around the problem is create another version of our private key that stripped out the passphrase. It's a workaround but does not fix the problem of passphrase not working in jenkins credential plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob.p.s. earlier I also added this line to java.security per plugin page but it did not fix it then:security.provider. 11 10 =org.bouncycastle.jce.provider.BouncyCastleProviderjenkins 1.625.3ssh agent plugin 1.9ssh credentials plugin 1.11java 8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Gro
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob. p.s. earlier I also added this line to java.security per plugin page but it did not fix it then:security.provider.11=org.bouncycastle.jce.provider.BouncyCastleProvider jenkins 1.625.3ssh agent plugin 1.9ssh credentials plugin 1.11 java 8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Group
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob.jenkins 1.625.3ssh agent plugin 1. 8 9 ssh credentials plugin 1.11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this host BldUser=jenkins build user SshUser=ssh user I think I fixed or found a way passed this problem. with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stan my guess is while this checks my private key it spits out a different version/type of the key?? If I use that private key for my ssh job my error goes away and it works. I added a new private key credential for SshUser with passphrase, leaving other one still there. But here is the weirdness or what I do not understand. BS node connects JM with old version SshUser key. on JM I have another ssh key for BldUser for the buildjob. In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work! Job does ssh -q somehost "hostname; pwd; id" id is for SshUser as I expect. but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses is from the BS ssh-agent setup (SshUser)! 17:51:15 [ssh-agent] Looking for ssh-agent implementation... 17:51:15 [ssh-agent] Java/JNR ssh-agent 17:51:17 [ssh-agent] Started. 17:51:17 [ssh-agent] Using credentials BldUser <- from buildjob 17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh 17:51:18 ++ hostname 17:51:18 + ssh -q somehost 'hostname; pwd; id' 17:51:18 somehost 17:51:18 /home/SshUser <- why from BS config (SshUser) and not from buildjob(BldUser)?? 17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx) 17:51:18 + rc=0 Is there some jenkins key caching and using going on here? If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob. jenkins 1.625.3 ssh agent plugin 1.8 ssh credentials plugin 1.11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [thinBackup] (JENKINS-21262) Allow Restore of Individual Jenkins Job Configs
Stan Towianski created JENKINS-21262 Allow Restore of Individual Jenkins Job Configs Issue Type: Bug Assignee: Thomas Fürer Components: thinBackup Created: 07/Jan/14 10:24 PM Description: I have used thin backup because it is thin, but I never wanted to restore All my project configs. I only wanted to restore single project configs that got messed up. In the restore I think it would be good to give a list of saved projects and let me pick 1 project or 'all' to restore. Project: Jenkins Priority: Major Reporter: Stan Towianski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
