Hi,
Is there a programmatical way to import a Trusted (Root CA) cert into
FireFox cert store besides through the PKCS#11 API ?
And, is there a programmtical way to edit the trust settings of a
Trusted (Root CA) cert ?
If none of the above works, how can I include our Trusted (Root CA) cert
into FireFox cert store under "Authority" ?
I am looking for work around ways to solve the following bug I reported:
Thanks,
8/21/06, So <oscarsoopensc (AT) gmail (DOT) comwrote:
Bob,
Regarding the bug:
Do you know who will be assigned to fix this bug ?
Thanks!
Best,
4/25/06, Bob Relyea <rrelyea (AT) redhat (DOT) comwrote:
So wrote:
Bob,
I just sent out three "talkback" bug reports
with my email, oscarsoopensc (AT) gmail (DOT) com.
Attached two screen shots for your reference.
I know that during edit trust settings event (i.e. certutil's
ChangeTrustAttributes), it goes down to the database to look for the
cert.
If I merely use "Import" button to import the Root cert into FF
"Authorities", edit trust settings will not crash.
Thanks,
Thanks Let's get a bug about this in mozilla then. Make sure I'm
CC'd on it and Kai Engert is CC'd. Write it against PSM for now, though
we may move it.
If it's possible to have a copy of the module that failed, that would be
great.
Thanks,
bob
4/25/06, So <oscarsoopensc (AT) gmail (DOT) comwrote:
>
>Bob,
>>
>"talkback report" ? Do you mean that Bug Report system ? Yes, I did
>click on send.
>Let me do three more now with my email:
>oscarsoopensc (AT) gmail (DOT) com
>so that you can find it easier.
>Also, please read my comment here:
>
>>
>Thanks,
>
>>
>4/25/06, Bob Relyea <rrelyea (AT) redhat (DOT) comwrote:
>>
So wrote:
Bob,
Attached the disassembly code, and an image of the crash point. I will
look into the Mozilla code as well.
Thanks,
Hmmm, the crash appears to happen in Firefox itself, not in PSM, NSS or
your PKCS #11 module. Did you allow a talkback report to go out?
(Firefox collects crashes, we can look them up based on email address
and get full symbol tracebacks).
bob
4/24/06, Bob Relyea <rrelyea (AT) redhat (DOT) comwrote:
SC (AT) gmail (DOT) com wrote:
Hi,
With my own implementation of PKCS#11 module,
FireFox crashed when I try edting the trust settings at Cert Manager.
Steps to reproduce:
1. PKCS#11 module reads the DER Root CA cert into the FireFox
"Authorities" store.
2. Go to FireFox Certificate Manager under "Authorities"
3. Click on the Root CA cert, and click "Edit" button below
4. There are no trust settings for all three checkboxes.
5. Do nothing
6. Click ""
7. FireFox crashed with the following error message:
The instruction at "0x" referenced memory at "0x0000000c".
The memory could not be "read".
I know there is some problem in my PKCS#11 implementation, but,
FireFox should not crash because of my bugs.
Can anyone help me on this one ?
Should I file a bug report ?
Where is the stack when the crash happens?
In general FF should be pretty resistant to bugs in the PKCS #11 module,
but the PKCS #11 module is loaded into the Firefox address space, so
bugs in the module itself can cause FF to crash.
Given the task you are doing, the place I would look first is what
happens in your C_C when you get an object type that you
don't understand.
bob

>
>
>
>
>
dev-tech-crypto mailing list
dev-tech-crypto (AT) lists (DOT) mozilla.org