On Thu, 17 Aug 2006, Norman Gray wrote:
> On 2006 Aug 17 , at 13.55, Mark Taylor wrote:
>
> >On Thu, 17 Aug 2006, Peter W. Draper wrote:
> >
> > >the top-level build.xml file: "ant keystore". Should really get some
> > >thirdparty certificates sometime, so people don't have to trust me.
> >
> >but you've got such an honest face.
>
> and commercial code-signing certificates cost $200 + $160/yr.
>
> http://www.thawte.com/ssl-digital-certificates/code-signing/index.html
> http://www.thawte.com/pricing/
Indeed. When all this first came up I thought someone said RAL had an
arrangement with some signer, but clearly that's now a bit useless.
> I don't know if NGS certificates can be used for code-signing. These
> are the `UK e-Science' certificates, but they might just be for hosts
> and services rather than code. It might be worth a try: while these
> roots aren't as well distributed as Verisign and co, they're better than
> nothing, and they'll become more fully distributed as time goes on.
> http://www.grid-support.ac.uk/content/view/84/35/
Err, thanks Norman, that page is as clear as mud. Looking around there do
seem to be ways of getting free certificates, CACert for instance.
Mark,
looking at the nightly build this change didn't fix things. I've tried to
reproduce the error, on my machine and at RAL, but to no avail. In an
attempt to just change anything and see what happens I've increased the
memory available to the <jarsigner> task and switched on some verbosity.
See what happens tomorrow,
Cheers,
Peter.
|