Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIXED JENKINS-30109] Update to bouncycastle 1.53 #8

Merged
merged 3 commits into from Oct 30, 2015

Conversation

seryl
Copy link
Contributor

@seryl seryl commented Aug 24, 2015

https://issues.jenkins-ci.org/browse/JENKINS-30109

Fixes issues connecting to ECDH ssl servers /w jdk8, perhaps other fixes.

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@recena
Copy link
Contributor

recena commented Aug 24, 2015

@seryl Could you add a Jira issue about this?

@seryl
Copy link
Contributor Author

seryl commented Aug 24, 2015

@seryl seryl changed the title Upgrade to bouncycastle 1.52 [FIXED JENKINS-30109] Upgrade to bouncycastle 1.52 Aug 24, 2015
@recena
Copy link
Contributor

recena commented Aug 24, 2015

@seryl Thanks so much. I'll try your proposal.

@recena
Copy link
Contributor

recena commented Aug 24, 2015

@seryl If you are working on this ticket, it would be interesting you accept the Jira ticket.

@recena recena changed the title [FIXED JENKINS-30109] Upgrade to bouncycastle 1.52 [FIXED JENKINS-30109] Added ECDH support Aug 24, 2015
@seryl
Copy link
Contributor Author

seryl commented Aug 26, 2015

@recena I'm not sure what you mean?

All of the work is done to get it finalized. Jenkins core also needed to be updated to 152, and as far as I'm aware jenkinsci/instance-identity-plugin#3 does that.

I can assign the tickets to myself in the Jenkins Jira, but they are already done and I don't have merge permissions; so I'm not sure how that helps..? Let me know what further steps I need to do to pull these in.

Eager to get this finished.

@recena
Copy link
Contributor

recena commented Aug 26, 2015

@seryl I've update JENKINS-30109 status.

@recena
Copy link
Contributor

recena commented Aug 26, 2015

@seryl I can merge this PR but I need to review it.

@seryl
Copy link
Contributor Author

seryl commented Sep 8, 2015

@recena Any chance you could look at this?

36 additions.
21 deletions.

@recena
Copy link
Contributor

recena commented Sep 8, 2015

@seryl Could you squash the commits?

} finally {
r.close();
}
} catch (Exception e) {
e.printStackTrace(listener.error(Messages.SSHAgentBuildWrapper_UnableToReadKey(e.getMessage())));
e.printStackTrace(listener.getLogger());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@seryl Why do you print listener.getLogger()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it to match the mirrored configuration on JNRRemoteAgent.java

https://github.com/jenkinsci/ssh-agent-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/JNRRemoteAgent.java#L101

If this is something you want, I assume you want it in both places.
If not, I assume you don't want it in either.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They should both be using the listener.error form

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we not want to print the getlogger then?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

listener.error also sends to getLogger but with the prefix message and allows for the two to be associated.

@seryl
Copy link
Contributor Author

seryl commented Sep 8, 2015

squashed and should be ready

@recena
Copy link
Contributor

recena commented Sep 9, 2015

@stephenc I agree with the changes. Your feedback will be great here.

@stephenc
Copy link
Member

stephenc commented Sep 9, 2015

Minor issue on logging. Would be great if a test could be included to prevent regressions. Otherwise looking good

@seryl
Copy link
Contributor Author

seryl commented Sep 9, 2015

@stephenc I'm not sure what you mean... do you want me to validate that it's printing errors when they occur?

If that's the case, I'll just remove that. I have little to no interest in getting that logging information in, I just want the bouncycastle updates. I just did it since that seemed like what the initial intention was.

@stephenc
Copy link
Member

@seryl I want you to test that ECDH keys do not blow up. A test with a test resource of an ECDH key that gets set as a credential and passed through the MinaAgent would suffice. Testing the logging information is not required.

@seryl
Copy link
Contributor Author

seryl commented Sep 22, 2015

I feel like there's some confusion..?

ECDH ssl is what we're adding support for here, not ecdsa keys.

We're allowing the key agreement when connecting to openssl servers to use the ecdh cipher.

This has nothing to do with openssh, so I don't understand why you are looking for a test on a new type of key?

This is to support downstream changes in the identity module.

Note: The original title was upgrade bouncycastle to 152; so that there would not be any confusion, which there seems to be.

Link to identity PR: jenkinsci/instance-identity-plugin#3

When both of these are added, we'll be able to connect to apache and nginx servers which are using the openssl ciphers such as: ECDHE-ECDSA-AES256-GCM-SHA384.

The only change provided here for openssh, is to use the new bouncycastle interfaces, nothing more.

@stephenc
Copy link
Member

Ahh ok, so you just want to bump the BC version (with the usual hassle of method signature changes)

OK... I'd prefer then if you update the PR title to reflect that as otherwise when we document the changes users will get confused just as I did

@seryl seryl changed the title [FIXED JENKINS-30109] Added ECDH support [FIXED JENKINS-30109] Update to bouncycastle 1.52 Sep 23, 2015
@seryl
Copy link
Contributor Author

seryl commented Sep 23, 2015

@stephenc Thanks for getting back to me, updated as requested

@seryl
Copy link
Contributor Author

seryl commented Sep 23, 2015

@stephenc jenkinsci/instance-identity-plugin#3 is the associated change, this should be the last of them to allow the upgrade to 152 for vanilla jenkins

@TheSavior
Copy link

Just like jenkinsci/instance-identity-plugin#3 this has been an issue for us as well and this fix works for us. Would be great to get this merged.

@seryl seryl changed the title [FIXED JENKINS-30109] Update to bouncycastle 1.52 [FIXED JENKINS-30109] Update to bouncycastle 1.53 Oct 30, 2015
@seryl
Copy link
Contributor Author

seryl commented Oct 30, 2015

@stephenc @recena Can we please give this some attention? It's been over 2 months now.

@stephenc
Copy link
Member

Still waiting for the requested changes to be made

@seryl
Copy link
Contributor Author

seryl commented Oct 30, 2015

I'm not sure I follow. What requested changes?

@stephenc
Copy link
Member

You removed the correct way of logging the stack trace in one of the lines you changed. I requested you to revert that change in the PR comment on that line

Sent from my iPhone

On 30 Oct 2015, at 6:54 p.m., Josh Toft notifications@github.com wrote:

I'm not sure I follow. What requested changes?


Reply to this email directly or view it on GitHub.

@seryl
Copy link
Contributor Author

seryl commented Oct 30, 2015

@stephenc removed as requested.

stephenc added a commit that referenced this pull request Oct 30, 2015
[FIXED JENKINS-30109] Update to bouncycastle 1.53
@stephenc stephenc merged commit 704e581 into jenkinsci:master Oct 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants