johst wrote, On 2008-09-11 18:31:
> I must apologise for wasting your time with something that was not
> really an issue. When you asked about whether I had downloaded the
> mozilla sources or used my distributor's (gentoo) I was about to
> answer that I downloaded the sources from mozilla.org and
I must apologise for wasting your time with something that was not
really an issue. When you asked about whether I had downloaded the
mozilla sources or used my distributor's (gentoo) I was about to
answer that I downloaded the sources from mozilla.org and built NSS
from there, but this prompted me
johst wrote, On 2008-09-11 16:39:
> Ok, thanks for the reply. Slowly I will build my understanding of this
> system and the tools. Attached is the output of modutil - i'm not too
> sure how to interpret it though:
>
> Listing of PKCS #11 Modules
> --
Ok, thanks for the reply. Slowly I will build my understanding of this
system and the tools. Attached is the output of modutil - i'm not too
sure how to interpret it though:
Listing of PKCS #11 Modules
---
1. NSS Internal PKCS #11 Module
Johan wrote, On 2008-09-11 09:45:
> I'm using NSS 3.12. I tried adding -p "mypassword" to the signtool
> command and it produced the same result.
OK. Then I'm wondering if your NSS installation is working at all.
Please try the command
modutil -list -dbdir .
where "." is the same directory yo
Hi again,
I'm using NSS 3.12. I tried adding -p "mypassword" to the signtool
command and it produced the same result. I also rebuilt NSS with
NSS_ENABLE_AUDIT=0 (just to make sure it's non FIPS), and again
received the same output. Any other ideas, suggestions? I'm really out
of my depth here sinc
johst wrote, On 2008-09-09 23:10:
> I'm getting the following when trying to sign a directory with html
> and javascript in:
What version of NSS are you using?
> $ signtool -d . -k "Absolute Security's VeriSign, Inc. ID" -Z
> download.jar download
> Generating download/META-INF/manifest.mf fil
Vladimir, Thanks for answering my questions.
I'm glad that you found a working solution.
> Suppose that information will help to improve NSS tools. Thanks again.
I filed these bugs in bugzilla:
> 390184 signtool fails when nickname contains colon, reports no more directory
> entries
> 390185 s
Nelson,
* Many thanks for the reply. I thought that "PvkTmp:
99ace907-0a0c-4066-bd60-751431d09f92" is too complex for the NSS and
tried to do something with it.
Problem was solved by changing friendly name of the cert. I added my
cert into IE certificates db, corrected field "friendly name" (the
[EMAIL PROTECTED] wrote:
Thanks for your message. It pointed out a number of all bugs in NSS.
I'm going to file bug reports on each of them that I found.
> I'm trying to sign Firefox plugin with a certificate. Cert is located
> in .pfx file. I successfully created local db and added my cert into
10 matches
Mail list logo
