stable

bouncycastle1.58-1.58-1.el6, canl-java-2.5.0-2.el6, & 3 more

FEDORA-EPEL-2018-71db8f6f28 created by ellert 6 years ago for Fedora EPEL 6

This update provides a parallel installable bouncycastle1.58 package. Like the Fedora bouncycastle package. this package provides all bouncycastle subpackages built from the same source package. Some of them were previously not available in EPEL 6.

The update also updates some packages to build against this new bouncycastle version, and adds canl-java and voms-clients-java to EPEL 6 which were previously not buildable due to missing dependencies.

This update has been submitted for testing by ellert.

6 years ago

ellert edited this update.

6 years ago

ellert edited this update.

New build(s):

  • bouncycastle-1.58-2.el6

Removed build(s):

  • bouncycastle-1.58-1.el6

Karma has been reset.

6 years ago

This update has been pushed to testing.

6 years ago

ellert edited this update.

New build(s):

  • voms-clients-java-3.0.7-6.el6

Removed build(s):

  • voms-clients-java-3.0.7-5.el6

Karma has been reset.

6 years ago

This update has been submitted for testing by ellert.

6 years ago

ellert edited this update.

New build(s):

  • voms-api-java-3.2.0-7.el6

Removed build(s):

  • voms-api-java-3.2.0-5.el6

Karma has been reset.

6 years ago

This update has been pushed to testing.

6 years ago
User Icon stevetraylen commented & provided feedback 6 years ago
karma

Great to see this at last.

BZ#1233527 bouncycastle-mail in EPEL 6
User Icon ceccanti commented & provided feedback 6 years ago
karma

While a recent version of BC in EPEL 6 it is welcome , this update will break many services in production on the WLCG due to backward incompatibilities and changes in package naming, so it needs to be carefully rolled-out.As a side note the versioning of voms-api-java and voms-clients in this update breaks a versioning convention that we use to keep versions aligned between voms-api-java, canl and bouncycastle and shield users of the voms-api-java to breaking changes in BC and CANL. I will send clarifications by email to Mattias with suggestions on how these problems could be fixed.

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

6 years ago
karma
User Icon evianello commented & provided feedback 6 years ago
karma

Due to its backward incompatibilities i'm down-voting this

I'd rather see any suggestions also in public. This realease seemed fine to me within an EPEL context.

Hello,

In EPEL (stable) there's: 1.46-1.el6 and this one jumps to 1.58-2.el6, as already mentioned it breaks a lot of stuff for us as well.

If it may help, here's the exact symptom:

1439 [main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED JettyGSIConnector7@0.0.0.0:8443: java.lang.VerifyError: (class: org/globus/gsi/bc/BouncyCastleOpenSSLKey, method: getKey signature: (Ljava/lang/String;[B)Ljava/security/PrivateKey;) Incompatible argument to function
java.lang.VerifyError: (class: org/globus/gsi/bc/BouncyCastleOpenSSLKey, method: getKey signature: (Ljava/lang/String;[B)Ljava/security/PrivateKey;) Incompatible argument to function
        at org.globus.gsi.X509Credential.loadKey(X509Credential.java:625)
        at org.globus.gsi.X509Credential.<init>(X509Credential.java:121)
        at gov.lbl.srm.server.JettyGSIConnector7.open(JettyGSIConnector7.java:344)
        at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:311)
        at org.eclipse.jetty.server.bio.SocketConnector.doStart(SocketConnector.java:151)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
        at org.eclipse.jetty.server.Server.doStart(Server.java:273)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
        at gov.lbl.srm.server.Server.mainJetty(Server.java:189)
        at gov.lbl.srm.server.Server.main(Server.java:95)

karma: -1

@steve: we keep the versioning aligned, so that - voms-api-java 3.0 depends on CANL 1.3.x which depends on BC 1.46 - voms-api-java 3.1 depends on CANL 2.1.x which depends on BC 1.50 - voms-api-java 3.2 depends on CANL 2.2.x which depends on BC 1.52 - voms-api-java 3.3 depends on CANL 2.5 which depends on BC 1.56 (even though apparently works fine also with 1.58)

It would be good if the EPEL packaging keeps this convention, so some changes to this update are required. Besides voms, bc 1.46 to 1.58 will for sure break other clients we are unaware of.

This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes

6 years ago

There are two solutions to this.

  1. Update bouncycastle as proposed in the update, but also add a bouncycastle1.46 compat package package that provides /usr/share/java/bcprov-1.46,jar that provides the old version.

  2. Leave the bouncycastle package at the old 1.46 version and add the update as a councycastle1.56 compat package with versioned jars.

Option 1 gives a cleaner state going forward, but option 2 is more backward compatible since it does not change the meaning of the unversioned /usr/share/java/bcprov,jar.

Do you have any preferences?

I vote for option 2

Review request bouncycastle1.58 compat package: https://bugzilla.redhat.com/show_bug.cgi?id=1539134 Anyone that can do a review?

ellert edited this update.

New build(s):

  • jglobus-2.1.0-5.el6
  • canl-java-2.5.0-2.el6
  • bouncycastle1.58-1.58-1.el6

Removed build(s):

  • bouncycastle-1.58-2.el6
  • canl-java-2.5.0-1.el6
  • jglobus-2.1.0-4.el6

Karma has been reset.

6 years ago

This update has been submitted for testing by ellert.

6 years ago

ellert edited this update.

6 years ago

This update has been pushed to testing.

6 years ago

ellert edited this update.

New build(s):

  • voms-clients-java-3.3.0-1.el6
  • voms-api-java-3.3.0-1.el6

Removed build(s):

  • voms-api-java-3.2.0-7.el6
  • voms-clients-java-3.0.7-6.el6

Karma has been reset.

6 years ago

This update has been submitted for testing by ellert.

6 years ago

This update has been pushed to testing.

6 years ago

This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes

6 years ago

This update has been submitted for batched by ellert.

6 years ago

This update has been submitted for stable by bodhi.

6 years ago

This update has been pushed to stable.

6 years ago

Please login to add feedback.

Metadata
Type
enhancement
Karma
0
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
6 years ago
in testing
6 years ago
in stable
6 years ago
modified
6 years ago
BZ#1233527 bouncycastle-mail in EPEL 6
0
0
BZ#1539134 Review Request: bouncycastle1.58 - Bouncy Castle Cryptography APIs for Java
0
0

Automated Test Results