On Tuesday, November 12, 2013 6:46:33 PM UTC+1, Mike Price wrote:
> We are trying to implement signing of xpi files using the NSS Signtool.exe.
> However, we need to access our certificate keys from our HSM server instead
> of having the keys installed in the local keystore on th
We are trying to implement signing of xpi files using the NSS Signtool.exe.
However, we need to access our certificate keys from our HSM server instead of
having the keys installed in the local keystore on the signing machine. Does
anyone have information on how to set this up and what the
Nelson,
Nelson B Bolyard wrote:
Beginning in NSS 3.11, loader always tries to load freebl using a full
absolute path name. It tries several path names, but it doesn't try to load
the simple shared library name.
That is not the case . loader always still tries the simple shared
library name,
Julien R Pierre - Sun Microsystems wrote, On 2008-11-12 14:46:
> The user above was using Windows, not Solaris. On Windows we didn't have
> freebl shared libs in 3.10, and thus no freebl library loading was
> necessary.
That's true for Windows.
> The simplest workaround for Windows users is t
Nelson,
Nelson B Bolyard wrote:
Two years ago this week, John Smith wrote to us:
When I sign using keytool.exe version 3.10 it signs OK,
When I sign using keytool.exe version 3.11 it throws this error:
using certificate directory: C:\Documents and
Settings\myusername\Application
Data\Moz
Two years ago this week, John Smith wrote to us:
> When I sign using keytool.exe version 3.10 it signs OK,
> When I sign using keytool.exe version 3.11 it throws this error:
>
> using certificate directory: C:\Documents and
> Settings\myusername\Application
> Data\Mozilla\Firefox\Profiles\vsw8
John Smith wrote:
I understand some of them, but not all. One part I don't understand is
why signtool 3.11 fails for you, but 3.10 doesn't.
You *might* be running into the same issue I ran into before. Try
setting a password on the db.
http://groups-beta.google.com/group/mozilla.dev.tech.cr
> I understand some of them, but not all. One part I don't understand is
> why signtool 3.11 fails for you, but 3.10 doesn't.
I have tried 3.10 with -X option and it works fine. 3.11 still gives the
same error message.
That's it. Works fine for me now.
Thank you.
__
t; What is it? Mine cert is marked as "code signing".
You may find the explanation here:
http://groups.google.com/groups/search?hl=en&q=signtool+%22object+signing%22+code&qt_s=Search
> This is my command line
>
> signtool.exe -d "C:\Docum...8mp7m.default" -k "CodeSig
When I sign using keytool.exe version 3.10 it signs OK, but when I try to
open my .xpi file with FF 2.0 it says that my .xpi is not signed.
When I sign using keytool.exe version 3.11 it throws this error:
using certificate directory: C:\Documents and
Settings\myusername\Application
Data\Mozil
r your cert?
Sure.
> Is your cert an object signing cert? Or merely code signing?
I am very surprised that there are "object" and "code" signing. I thought
only "code signing" existed. I have never heard for "object signing" before.
What is it? Mine c
John Smith wrote:
> When I execute signtool.exe I got this error:
>
> using certificate directory: C:\Documents and
> Settings\myusername\Application
> Data\Mozilla\Firefox\Profiles\vsw8mp7m.default
That's your firefox profile.
You're not running signtool while
When I execute signtool.exe I got this error:
using certificate directory: C:\Documents and
Settings\myusername\Application
Data\Mozilla\Firefox\Profiles\vsw8mp7m.default
signtool: function failed: An I/O error occurred during security
authorization.
I belived my keystore was corrupted, so I
13 matches
Mail list logo