can i force that a bundle/jar must come from a specific location specified in the target file? #566
Replies: 5 comments 11 replies
-
You can also sign your product with jarsigner. Or you can build your product from the generated updatesite in a separate reactor project. |
Beta Was this translation helpful? Give feedback.
-
No, you can't. It's part of the fun with p2. |
Beta Was this translation helpful? Give feedback.
-
Yes, those units are "fake" units that you tampered but kept their "official" coordinates. That's not a good practice, it's better to just create new units in that case (eg prefix Bundle-SymbolicName with
If you find out which one, please report to the providing project. |
Beta Was this translation helpful? Give feedback.
-
I've been saying Orbit is wrong for a long time, nothing new here ;) And to be honest my latest investments towards PGP signatures have for side-effect goal to turn Orbit useless and make it disappear.
Actually, the unsigned one is the right one, yours is a tampered version that uses "official" coordinates for different content, maybe adding some malicious code in it to run a botnet, who knows? (I trust you're not doing anything malicious, it's just an illustration of how a different artifact with official coordinates can be interpreted per se an unsafe)
If you use a recent Eclipse Platform/p2 and configure it so your signer public key is trusted by default, then yes, it will be interpreted as signed during the installation.
It helps in the sense that you won't have 2 different artifacts for the same p2 coordinates. It disambiguates everything.
Not much beyond the mojo description. But specific questions (and contributions to improve that doc) are welcome. |
Beta Was this translation helpful? Give feedback.
-
OK, so PGP signatures cover that part well. |
Beta Was this translation helpful? Give feedback.
-
Hi,
i have an annoying thing that we do make a p2 site of all kinds of 3rd party plugins:
https://github.com/Servoy/servoy-eclipse/blob/master/shipplugins/category.xml
and i use the feature of tycho that i use signing: https://github.com/Servoy/servoy-eclipse/blob/master/shipplugins/pom.xml#L81 and then fix the artifacts:https://github.com/Servoy/servoy-eclipse/blob/master/shipplugins/pom.xml#L121
to get a nice fully signed p2 site that i then use in my target:
https://github.com/Servoy/servoy-eclipse/blob/master/launch_targets/com.servoy.eclipse.target.target#L6
(i even have it on top of the file, hoping that order would do something)
but when i build my product with that target:
it should get these nicely signed files:
https://developer.servoy.com/p2_repository/ship_plugins/2022.03/plugins/org.apache.commons.commons-text_1.9.0.jar
https://developer.servoy.com/p2_repository/ship_plugins/2022.03/plugins/org.apache.commons.commons-fileupload_1.4.0.jar
but the end result of the full products p2 site:
https://download.servoy.com/developer/latest/plugins/org.apache.commons.commons-text_1.9.0.jar
https://download.servoy.com/developer/latest/plugins/org.apache.commons.commons-fileupload_1.4.0.jar
are suddenly different files.. that are not signed.
So if somebody now does a upgrade of our product they get a warning of unsigned content..
not sure which target it gets it from, mostly are just hard coded versions of jars, but also of features so i guess it could ride with something.
But i really want to force to get it from my p2 site...
Beta Was this translation helpful? Give feedback.
All reactions