Generally the most useful information is in bugzilla.
From reading
https://bugzilla.mozilla.org/show_bug.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&id=427715
it appears the bug is still open .
Ruchi Lohani wrote:
> Hi,
>
> Is the bug filed with number 427715 fixed. The b
Hi,
Is the bug filed with number 427715 fixed. The browser is crashing because
of NSS.
It would be great if somebody can tell me about it.
Thanks
Ruchi
___
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo
Nelson B Bolyard wrote:
> Michael Kaply wrote:
>> For the record, I just checked my Windows machine (where all this works)
>>
>> It's NSS 3.11
>>
>> The extra "thawte" is not in the database
>>
>> c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
>> Thawte Code Signing CA - Thawte
Julien R Pierre - Sun Microsystems wrote:
> Michael,
>
> Michael Kaply wrote:
>> I was using 3.12 which is the only 3.12 version available here
>>
>> ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/
>>
>>
>
> OK. 3.12.1 was very recently released (last week), but I guess we
> haven't
Michael Kaply wrote:
> For the record, I just checked my Windows machine (where all this works)
>
> It's NSS 3.11
>
> The extra "thawte" is not in the database
>
> c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
> Thawte Code Signing CA - Thawte Consulting ccc,
Michael,
Michael Kaply wrote:
>
> I was using 3.12 which is the only 3.12 version available here
>
> ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/
>
>
OK. 3.12.1 was very recently released (last week), but I guess we
haven't uploaded a source tarball for it yet.
If you have a
Mike,
Michael Kaply wrote:
> For the record, everything works fine with an NSS 3.12 that I built on
> my machine.
>
> So I don't know if it is an NSS 3.11 problem (which might be the case
> since other people have reported it) or a problem with darwin ports
> (which I doubt)
>
> Mike Kaply
F
Julien R Pierre - Sun Microsystems wrote:
> Mike,
>
> Michael Kaply wrote:
>> For the record, everything works fine with an NSS 3.12 that I built on
>> my machine.
>>
>> So I don't know if it is an NSS 3.11 problem (which might be the case
>> since other people have reported it) or a problem wit
For the record, I just checked my Windows machine (where all this works)
It's NSS 3.11
The extra "thawte" is not in the database
c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
Thawte Code Signing CA - Thawte Consulting ccc,,c
I used exactly the same PFX file
Mike,
Michael Kaply wrote:
> For the record, everything works fine with an NSS 3.12 that I built on
> my machine.
>
> So I don't know if it is an NSS 3.11 problem (which might be the case
> since other people have reported it) or a problem with darwin ports
> (which I doubt)
>
> Mike Kaply
T
Michael Kaply wrote:
> Nelson B Bolyard wrote:
>> what does
>> certutil -d ~ -L
>> output?
>
> c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
> Thawte Code Signing CA - Thawte Consulting ccc,c,c
> thawte c
Nelson B Bolyard wrote:
> Michael Kaply wrote:
>> Nelson B Bolyard wrote:
>
>>> what does
>>> certutil -d ~ -L
>>> output?
>> c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
>> Thawte Code Signing CA - Thawte Consulting ccc,c,c
>> thawte
Nelson B Bolyard wrote:
> Michael Kaply wrote:
>> Wan-Teh Chang wrote:>
>>> Please provide the signtool command line you used, and the
>>> content of the relevant directories.
>>>
>>> "An I/O error occurred during security authorization" is
>>> SEC_ERROR_IO. This error often has nothing to do
>>>
With NSS 3.12 it looks like this after import (and works)
c1dfd405-9dc0-4b7c-8e98-7b2772a81922 u,u,u
Thawte Code Signing CA - Thawte Consulting cc,,
___
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.or
For the record, everything works fine with an NSS 3.12 that I built on
my machine.
So I don't know if it is an NSS 3.11 problem (which might be the case
since other people have reported it) or a problem with darwin ports
(which I doubt)
Mike Kaply
__
Michael Kaply wrote:
> Wan-Teh Chang wrote:>
>> Please provide the signtool command line you used, and the
>> content of the relevant directories.
>>
>> "An I/O error occurred during security authorization" is
>> SEC_ERROR_IO. This error often has nothing to do
>> with I/O. SEC_ERROR_IO is report
Gervase Markham:
> Eddy Nigg wrote:
>> I wouldn't state it this way, otherwise we urgently need to modify the
>> Mozilla CA policy! An attacker shouldn't be successful in such an
>> attempt and CAs should have controls in place to detect such attempts.
>
> If that's true, then what controls to Star
Wan-Teh Chang wrote:>
> Please provide the signtool command line you used, and the
> content of the relevant directories.
>
> "An I/O error occurred during security authorization" is
> SEC_ERROR_IO. This error often has nothing to do
> with I/O. SEC_ERROR_IO is reported when
> libsoftokn3.dylib
On Wed, Aug 27, 2008 at 8:34 AM, Michael Kaply <[EMAIL PROTECTED]> wrote:
> I'm having a problem signing my Firefox extension on Mac OS X. The error
> I get is:
>
> signtool: function failed: An I/O error occurred during security
> authorization.
>
>
> I built NSS and NSPR myself using Darwin Ports
Eddy Nigg wrote:
> I wouldn't state it this way, otherwise we urgently need to modify the
> Mozilla CA policy! An attacker shouldn't be successful in such an
> attempt and CAs should have controls in place to detect such attempts.
If that's true, then what controls to Startcom (to take an example)
I'm having a problem signing my Firefox extension on Mac OS X. The error
I get is:
signtool: function failed: An I/O error occurred during security
authorization.
I built NSS and NSPR myself using Darwin Ports
sudo port install nspr (4.7_1)
sudo port install nss (3.11.9_0)
I have had no
Hi,
basically, I want to play around with EVN for documentation and
development purposes, and the only way of getting a "cheap"
certificate is creating one on my own... so a pointer would be
welcome.
Thanks
Jakob
___
dev-tech-crypto mailing list
dev-tec
Hi,
Before posting a bug I will rebuild the NSS with complete set of
elliptic curves from NSS_3_11_1_RTM, and than try to create another
certificate request, sign-it and import it again.
My previous build was based on 3.12 with update based on solaris
ecl-curve.h, I've run diff, and it seams that
23 matches
Mail list logo
