Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] p2 repositories and signing

Thanks for the reference, Pascal. I have re-phrased and re-opened the bug. The discussion seemed to have stalled based on security implications of having the signing key more widely available, where in my opinion that isn’t the central aspect of the requirement.


Since signed deliverables is a requirement for participating on the release train, it is imperative that this is made a simple as possible. Most of the projects trying to participate in the release train don’t have dedicated releng person to continually mess with all of this.


- Konstantin



From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Thursday, January 06, 2011 1:31 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] p2 repositories and signing


I've run into the same issues a few weeks back and have opened:


On 2011-01-06, at 4:26 PM, Konstantin Komissarchik wrote:

Thanks, but that’s not quite what I am asking. If I can sign from the middle of my build on Hudson, I can do that before building the repository metadata in the first place.


My question is how do I sign from the middle of the build process running on Hudson. Signing requires committer credentials, ssh to, etc. Seems incompatible with doing this during the build, yet the result needs to be post-processed after signing to be usable.


Seems rather unnecessarily complicated. Can we have a blocking signing script available on Hudson hosts that would use host/hudson credentials?


- Konstantin



From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim Moir
Sent: Thursday, January 06, 2011 1:11 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] p2 repositories and signing



You can to use the p2.process.artifacts  task to update the MD5 signatures of the bundles in your repo once they've been signed 

In our build, we run it like this which updates the checksums and also creates packed files in the repo 

<p2.process.artifacts repositoryPath="file://${yourrepo}" pack="true" /> 


From:        "Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx> 
To:        "'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx> 
Date:        01/06/2011 03:39 PM 
Subject:        [cross-project-issues-dev] p2 repositories and signing 
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

I’d like to hear how people handle signing of p2 repositories. My project build produces a p2 repository archive. For my first attempt, I used sign script to sign the repository… Oops… The p2 repository is now corrupted. Understandable in retrospect. Signing changes the plugin and feature jars. The checksums stored in p2 metadata no longer match. 
So, it seems that one must perform signing in the middle of the build process running on Hudson. How would I do this given the convoluted signing infrastructure we have to use? 
- Konstantin_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list


Back to the top