You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Jeff MAURY (JIRA)" <ji...@apache.org> on 2014/09/12 09:45:33 UTC
[jira] [Commented] (SM-2369) Common bundles under
org.apache.servicemix.bundles signed with expired certificate
[ https://issues.apache.org/jira/browse/SM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131226#comment-14131226 ]
Jeff MAURY commented on SM-2369:
--------------------------------
Update on this: this seems to be specific to bouncycastle as I've checked the other under bundles (cglib, commons-beanutils, commons-validator, dnsjava, javax.mail and oro) and they are not signed.
> Common bundles under org.apache.servicemix.bundles signed with expired certificate
> ----------------------------------------------------------------------------------
>
> Key: SM-2369
> URL: https://issues.apache.org/jira/browse/SM-2369
> Project: ServiceMix
> Issue Type: Bug
> Reporter: Jeff MAURY
>
> I'm using some of the bundles under the org.apache.servicemix.bundles groupId in our Eclipse based product. I noticed that some of them (at least this is true for org.apache.servicemix.bundles.bcpg-jdk15on/1.50_1) are signed with an expired certificate (2012) that may cause users to be troubled during installation/update
> I would prefer to have it not signed at all than signed with an expired certificate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)