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
slots: 2 slots attached
status: loaded
slot: NSS Internal Cryptographic
Services
token: NSS Generic Crypto Services
slot: NSS User Private Key and Certificate
Services
token: NSS Certificate DB
-----------------------------------------------------------
On Sep 11, 8:31 pm, Nelson B Bolyard <[EMAIL PROTECTED]> wrote:
> 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 you used before in your signtool command,
> and send the output from that command.
>
> > I also rebuilt NSS with NSS_ENABLE_AUDIT=0 (just to make sure it's non
> > FIPS),
>
> Well, NSS_ENABLE_AUDIT controls the run time behavior, not the build.
> It has no effect on the build, and at run time, it only enables auditing.
> So, it really has no effect on whether you're running in "FIPS mode" or not.
>
> The output of modutil as requested above will tell us much.
_______________________________________________
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
