Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » site signing asks for keystore passphrase
site signing asks for keystore passphrase [message #639199] Mon, 15 November 2010 15:27 Go to next message
Jesper Eskilson is currently offline Jesper EskilsonFriend
Messages: 134
Registered: July 2009
Senior Member
I'm trying to get local signing to work in our nightly build, but it
asks me for the keystore password, despite local.keystore.password being
set in the buckminster.properties file.

> site.signing=true
> signing.type=local
> local.keystore.path=/home/jesperes/dev/eclipse/keystore
> local.keystore.alias=jesperes
> local.keystore.password=hubble

When executing my ant script which drives the build, it repeatedly asks
for the passphrase:

> [java] INFO: [start com.iar.hubble.product.arm.feature:eclipse.feature$1.0.0.qua lifier#site.signed]
> [java] [ant] Enter Passphrase for keystore:
> [java] [ant] Enter Passphrase for keystore:
> [java] [ant] Enter Passphrase for keystore:

....

> [java] [ant] Enter Passphrase for keystore:
> [java] [ant] Enter Passphrase for keystore:
> [java] [ant] Enter Passphrase for keystore:
> [java] [ant] Enter Passphrase for keystore:
> [java] INFO: [end com.iar.hubble.product.arm.feature:eclipse.feature$1.0.0.qua lifier#site.signed]

The site seems to be become signed ok, but why does it print out the
prompts?


--
Jesper Eskilson
Developer
IAR Systems
Re: site signing asks for keystore passphrase [message #639215 is a reply to message #639199] Mon, 15 November 2010 15:45 Go to previous messageGo to next message
Thorsten Meinl is currently offline Thorsten MeinlFriend
Messages: 85
Registered: July 2009
Member
Am 15.11.2010 16:27, schrieb Jesper Eskilson:
> The site seems to be become signed ok, but why does it print out the
> prompts?
This is normal behaviour. Signing usually happens by spawning a separate
process which prompts for the password and gets it via stdin from the
ant-script behind the scenes. Nothing to worry about.

Cheers,

Thorsten
Re: site signing asks for keystore passphrase [message #639278 is a reply to message #639215] Mon, 15 November 2010 21:30 Go to previous messageGo to next message
Alex Kravets is currently offline Alex KravetsFriend
Messages: 561
Registered: November 2009
Senior Member
I have the same issue, and was wondering too how come it asks so many times for passphrase. Last time I counted prompt was printed 72 times and this adds 5-6 minutes to total build time. Is there something I can do about this?

thanks,
Alex
Re: site signing asks for keystore passphrase [message #639291 is a reply to message #639278] Mon, 15 November 2010 21:53 Go to previous messageGo to next message
Thorsten Meinl is currently offline Thorsten MeinlFriend
Messages: 85
Registered: July 2009
Member
Am 15.11.2010 22:30, schrieb Alex:
> I have the same issue, and was wondering too how come it asks so many
> times for passphrase. Last time I counted prompt was printed 72 times
> and this adds 5-6 minutes to total build time. Is there something I can
> do about this?
Well, it asks for each plugin and feature that is to be signed. If you
want signing you need to be patient ;-) One "problem" is that *all* jars
are signed, not only yours but also the ones from external sources such
as Eclipse. This could be the reason you are seeing so many invocations
of signjar.
This can be changes by using a custom site.signed action that only signs
selected jars.
Re: site signing asks for keystore passphrase [message #639352 is a reply to message #639215] Tue, 16 November 2010 08:38 Go to previous messageGo to next message
Jesper Eskilson is currently offline Jesper EskilsonFriend
Messages: 134
Registered: July 2009
Senior Member
On 11/15/2010 04:45 PM, Thorsten Meinl wrote:
> Am 15.11.2010 16:27, schrieb Jesper Eskilson:
>> The site seems to be become signed ok, but why does it print out the
>> prompts?
> This is normal behaviour. Signing usually happens by spawning a separate
> process which prompts for the password and gets it via stdin from the
> ant-script behind the scenes. Nothing to worry about.

Ok, thanks.

--
Jesper Eskilson
Developer
IAR Systems
Re: site signing asks for keystore passphrase [message #639449 is a reply to message #639291] Tue, 16 November 2010 15:29 Go to previous messageGo to next message
Alex Kravets is currently offline Alex KravetsFriend
Messages: 561
Registered: November 2009
Senior Member
Thorsten Meinl wrote on Mon, 15 November 2010 16:53
Am 15.11.2010 22:30, schrieb Alex:
> I have the same issue, and was wondering too how come it asks so many
> times for passphrase. Last time I counted prompt was printed 72 times
> and this adds 5-6 minutes to total build time. Is there something I can
> do about this?
Well, it asks for each plugin and feature that is to be signed. If you
want signing you need to be patient Wink One "problem" is that *all* jars
are signed, not only yours but also the ones from external sources such
as Eclipse. This could be the reason you are seeing so many invocations
of signjar.
This can be changes by using a custom site.signed action that only signs
selected jars.


Thanks, I'll look at customer signer then.
Re: site signing asks for keystore passphrase [message #649152 is a reply to message #639291] Mon, 17 January 2011 22:32 Go to previous messageGo to next message
Chris Eagan is currently offline Chris EaganFriend
Messages: 15
Registered: July 2009
Junior Member
I am confused about how exactly you go about creating a custom site.signed action. I have run into problems when I create my own action with the same name like "site.signed" because buckminster complains that the action already exists.

The site.p2 action uses site.signed in it's prerequisites and uses the "site" that it produces. If I could create an action that site.p2 would use as the site, then I think that would work, but I cannot find anything about adding prerequisites to the existing actions.

I created a custom site.p2 action almost exactly like the original and only changed the prerequisites section to call site.signed.custom instead of site.signed. I then did the same thing with site.signed and instead made it call build/signing.ant instead of the built in signing script.

	<public name="site.p2.custom" actor="p2SiteGenerator">
            <prerequisites>
                <attribute name="manifest" alias="site.definer"/>
                <attribute name="product.configuration.exports" alias="product.configs"/>
                <attribute name="site.feature.exports" alias="site" filter="(&amp;(!(site.pack200=true))(!(site.signing=true)))"/>
                <attribute name="site.packed" alias="site" filter="(site.pack200=true)"/>
                <attribute name="site.signed.custom" alias="site" filter="(&amp;(site.signing=true)(!(site.pack200=true)))"/>
            </prerequisites>
            <products base="${buckminster.output}/site.p2/" upToDatePolicy="ACTOR"/>
        </public>
        <public name="site.signed.custom" actor="ant">
            <actorProperties>
                <property key="buildFile" value="build/signing.ant"/>
                <property key="targets" value="sign.jars"/>
            </actorProperties>
            <prerequisites alias="action.requirements">
                <attribute name="site.repacked" filter="(site.pack200=true)"/>
                <attribute name="site.feature.exports" filter="(!(site.pack200=true))"/>
            </prerequisites>
            <products alias="action.output" base="${buckminster.output}/site.signed/" upToDatePolicy="MAPPER"/>
        </public>


I copied the script from "<eclipse-install> \plugins\org.eclipse.buckminster.jarprocessor_1.0.0.r11559.j ar\org\eclipse\buckminster\jarprocessor\antscript\signing.an t " and changed the line that signed all jars to only sign my plugins
Re: site signing asks for keystore passphrase [message #649600 is a reply to message #649152] Wed, 19 January 2011 20:17 Go to previous message
Thorsten Meinl is currently offline Thorsten MeinlFriend
Messages: 85
Registered: July 2009
Member
Am 17.01.2011 23:32, schrieb Chris Eagan:
> I am confused about how exactly you go about creating a custom
> site.signed action.
You need to remove the "old" action in addition to providing your own
customized action:

<cspecExtension xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
xmlns="http://www.eclipse.org/buckminster/CSpec-1.0">
<actions>
<public name="site.signed" actor="ant">
<actorProperties>
<property key="buildFileId" value="knime.signing" />
<property key="targets" value="sign.jars" />
</actorProperties>
<prerequisites alias="action.requirements">
<attribute name="site.repacked" filter="(site.pack200=true)" />
<attribute name="site.feature.exports"
filter="(!(site.pack200=true))" />
</prerequisites>
<products alias="action.output"
base="${buckminster.output}/site.signed/"
upToDatePolicy="MAPPER" />
</public>
</actions>
<alterActions>
<remove name="site.signed" />
</alterActions>
</cspecExtension>
Previous Topic:ERROR: Plug-in org.eclipse.jsch.core was unable to load
Next Topic:Possibly odd RMAP question
Goto Forum:
  


Current Time: Sat Sep 18 08:22:25 GMT 2021

Powered by FUDForum. Page generated in 0.02758 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top