Notice: Signature Verification Errors on Older Eclipse Versions

Target: Older Eclipse versions (e.g., 2018‑09 (4.9))
Example Issue: When installing a plugin signed in 2025, an error may occur during signature verification, causing the installation to fail.

＊Note: If no improvements,please use a Eclipse version that is listed in the system requirements page of CDE.

Error Message (Summary)

An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,com.curl.eclipse.cde.mat.hprof,8.0.15001.v2025-09-17-222006.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile4945995344152765921.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile4945995344152765921.jar
Problems downloading artifact: org.eclipse.update.feature,com.curl.eclipse.cde.mat.hprof.feature,8.0.15001.v2025-09-17-222006-7H-MJm8s737D13L15H177733F.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile5794029699063839755.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile5794029699063839755.jar
Problems downloading artifact: osgi.bundle,com.curl.eclipse.cde.uml,8.0.15001.v2025-09-17-222006.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile4963073679208978907.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile4963073679208978907.jar
Problems downloading artifact: org.eclipse.update.feature,com.curl.eclipse.cde.uml.feature,8.0.15001.v2025-09-17-222006-7H-MJm8s737D13L15H177733F.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile1271301543046650798.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile1271301543046650798.jar
Problems downloading artifact: org.eclipse.update.feature,com.curl.eclipse.cde.win32.en,8.0.15001.v2025-09-17-222006-79-IeO7w313601A0280333117.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile1667298582133947698.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile1667298582133947698.jar
Problems downloading artifact: org.eclipse.update.feature,com.curl.eclipse.cde.win32.ja,8.0.15001.v2025-09-17-222006-79-IeO7w313601A0280333117.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile3084116716293076525.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile3084116716293076525.jar
Problems downloading artifact: osgi.bundle,com.curl.eclipse.plugin,8.0.15001.v2025-09-17-222006.
Error reading signed content:C:\Users\localuser\AppData\Local\Temp\signatureFile3612675547607490272.jar
An error occurred while processing the signatures for the file: C:\Users\localuser\AppData\Local\Temp\signatureFile3612675547607490272.jar

Summary of Causes

• Compatibility Issues with Old p2 Engine: Eclipse provisioning (p2) uses signature formats (JAR or PGP) and verification methods that differ by version. Older Eclipse versions may fail to verify newer certificates/signatures. [1]
• Mismatched Trust Store: If the JRE’s cacerts does not include the root/intermediate certificates used for signing, or if corporate proxy/SSL inspection replaces certificates, the signature will be considered “untrusted.”
• Known “Error reading signed content” Issue: Errors during signed content reading/verification cause installation failures. [2]

Recommendation: Update Eclipse to a newer release (e.g., 2021‑03 or later) to improve p2 signature handling and compatibility. [1]

---

Temporary Workaround (Relax Signature Verification)

This is not a permanent solution and involves security risks. If you need to proceed with installation, add the following setting to eclipse.ini to relax signature verification policy:

1. Exit Eclipse.
2. Edit eclipse.ini (each option on a separate line; options below -vmargs are passed to the JVM). [3]-vmargs:

   -vmargs
   -Declipse.p2.unsignedPolicy=allow
   

   • This property relaxes p2’s trust policy to allow unsigned/untrusted content.
     Note: It will not fix cases where the signature itself is broken or invalid. [4]
3. Save and restart Eclipse, then retry installation.

Warning: This setting allows installation of untrusted content. It is strongly recommended to revert this setting after installation. [4]

Additional Notes

• Refer to Eclipse official documentation for eclipse.ini editing rules and -vmargs usage. [3][1]