[MAGNOLIA-5892] Update Bouncy Castle dependencies to jdk15on-1.46 releases Created: 18/Aug/14  Updated: 02/Jul/15  Resolved: 01/Jul/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.2.7, 5.3.2
Fix Version/s: 5.4

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Michael Mühlebach
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
supersession
is superseded by MAGNOLIA-6279 Update Bouncy Castle encryption libs ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Update 3rd party libs for 5.4

 Description   

bc jdk16 (release 1.46) currently used by Magnolia is much older than the most current released bc jdk15on (release 1.51).

Keep in mind the jdk15on is for JDK 1.5 - JDK 1.7 (see http://www.bouncycastle.org/latest_releases.html)

bouncycastle is used in core and magnolia-license modules. Please check for other uses as well.



 Comments   
Comment by Magnolia International [ 10/Nov/14 ]

This has at least implications, on the top of my head, on:

  • core (but for what ?)
  • activation (keys and encryption)
  • license (decoding)
  • license generation
    Make sure all these are covered
Comment by Michael Mühlebach [ 13/Nov/14 ]

One part of the update has been forgotten in license and license-generator. It is now implemented but because of the errors in activation the change can not be tested and is parked in the feature branch.

Comment by Mikaël Geljić [ 29/May/15 ]

How about now? Can we get this out of sight?

Comment by Michael Mühlebach [ 01/Jun/15 ]

It went a little bit out of sight ... at least for me
I start integrating it right away and hope nothing huge has change meanwhile.

Comment by Michael Mühlebach [ 02/Jun/15 ]

mgeljic: I talked shortly to pmundt and he thought, we should focus rather on the remaining stuff for the beta than introduce an additional problem area. I agree with him on that.
I looked again at the original support ticket and have seen, that we already did solve it because it asked us to switch from the deprecated jdk16 bc branch to the jdk15on branch. And we did this already long ago.

What remains is updating to the newest Version and we could move this to 5.5?
If it is okay with everybody I would rephrase this ticket to address just the bcpg-jdk16 -> bkpg-jdk15on move and add a superseding ticket for 5.5 for the update from version 1.46 to 1.52 (or whatever is the current version).

Comment by Magnolia International [ 01/Jul/15 ]

Master is now using bcmail-jdk15on-1.46, bcpg-jdk15on-1.46 and bcprov-jdk15on-1.46

Generated at Mon Feb 12 04:09:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.