Re: [cross-project-issues-dev] To be able to install newly signed plug-in on Helios and Indigo

2015-04-20 Thread Thomas Watson
If you really cannot move up to at least the Juno release then the 2 
following options area available:

1) remove the signatures from the jars and place them on your own update 
sight to install from ... or
2) patch equinox (org.eclipse.osgi) with 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378155

Tom





From:   Grégoire Dupé 
To: "'Cross project issues'" 
Date:   04/20/2015 05:04 AM
Subject:    [cross-project-issues-dev] To be able to install newly 
signed  plug-in on Helios and Indigo
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hello,
 
We are not able to install newly signed plug-ins on Helios, and Indigo. We 
get the following error (during the installation of a signed plug-in): 
Caused by: java.security.NoSuchAlgorithmException: No algorithm found for 
2.16.840.1.101.3.4.2.1
at 
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.findDigest(PKCS7Processor.java:87)
at 
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.processSignerInfos(PKCS7Processor.java:311)
at 
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.(PKCS7Processor.java:133)
at 
org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:93)
at 
org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:60)
at 
org.eclipse.osgi.internal.signedcontent.SignedBundleFile.setBundleFile(SignedBundleFile.java:47)
at 
org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:247)
 
This error happens because the class ‘PKCS7Processor’ embedded in Helios 
and Indigo isn’t able to deal with SHA-256. SHA-256 is used since Java-1.7 
to sign [1]. I assume that the signing service has been updated to 
Java-1.7.
 
From the release train point of view this seems to be a good thing. But my 
company integrates EMF Facet and MoDisco into its own product and some of 
our clients are still using Helios and Java-1.5! 
 
Does anybody have any advice to be able to install newly signed plug-in on 
Helios and Indigo?
 
Regards,
Grégoire Dupé___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] To be able to install newly signed plug-in on Helios and Indigo

2015-04-20 Thread Grégoire Dupé
Hello,



We are not able to install newly signed plug-ins on Helios, and Indigo. We
get the following error (during the installation of a signed plug-in):

Caused by: java.security.NoSuchAlgorithmException: No algorithm found for
2.16.840.1.101.3.4.2.1

at
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.findDigest(PKCS7Pro
cessor.java:87)

at
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.processSignerInfos(
PKCS7Processor.java:311)

at
org.eclipse.osgi.internal.signedcontent.PKCS7Processor.(PKCS7Process
or.java:133)

at
org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSig
ner(SignatureBlockProcessor.java:93)

at
org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(Si
gnatureBlockProcessor.java:60)

at
org.eclipse.osgi.internal.signedcontent.SignedBundleFile.setBundleFile(Sig
nedBundleFile.java:47)

at
org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(
SignedBundleHook.java:247)



This error happens because the class ‘PKCS7Processor’ embedded in Helios
and Indigo isn’t able to deal with SHA-256. SHA-256 is used since Java-1.7
to sign [1]. I assume that the signing service has been updated to
Java-1.7.



>From the release train point of view this seems to be a good thing. But my
company integrates EMF Facet and MoDisco into its own product and some of
our clients are still using Helios and Java-1.5!



Does anybody have any advice to be able to install newly signed plug-in on
Helios and Indigo?



Regards,

Grégoire Dupé

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev