Re: Step-by-step instructions on creating test email certificates

Nelson Bolyard wrote: > > Not sure, but I think it's this bug: > Bug 252250 – Incorrect handling of S/MIME keys with multiple identities > (need UI for per-identity cert settings) > > OK, I see the problem this bug describes. -- Regards Signer: Eddy Nigg, StartCom Ltd.

Re: Step-by-step instructions on creating test email certificates

Eddy Nigg (StartCom Ltd.) wrote, On 2008-02-20 18:39: > Nelson B Bolyard wrote: >> Neil wrote, On 2008-02-20 16:33: >> >>> I've been asked to review a patch that enhances the multiple identity UI >>> in Thunderbird/SeaMonkey by allowing email certificates to be selected >>> on a per-identity b

Re: Step-by-step instructions on creating test email certificates

Nelson B Bolyard wrote: > Neil wrote, On 2008-02-20 16:33: > >> I've been asked to review a patch that enhances the multiple identity UI >> in Thunderbird/SeaMonkey by allowing email certificates to be selected >> on a per-identity basis, rather than just for the main identity. >> >> It seems

Re: Looking for details about PR_Init argument maxPTDs

On Tue, Feb 19, 2008 at 7:02 PM, D3!$ <[EMAIL PROTECTED]> wrote: > > In fact, it is no longer necessary to call PR_Init(). NSPR is now > > implicitly > > initialized, usually by the first NSPR function the program calls. > > I believe that the above fact(and those like these..) should be >

Re: Step-by-step instructions on creating test email certificates

Neil wrote, On 2008-02-20 16:33: > I've been asked to review a patch that enhances the multiple identity UI > in Thunderbird/SeaMonkey by allowing email certificates to be selected > on a per-identity basis, rather than just for the main identity. > > It seems that building SeaMonkey will includ

Step-by-step instructions on creating test email certificates

I've been asked to review a patch that enhances the multiple identity UI in Thunderbird/SeaMonkey by allowing email certificates to be selected on a per-identity basis, rather than just for the main identity. It seems that building SeaMonkey will include certutil which looks as if it is more th

Re: QuoVadis request for root upgrade to EV

Frank Hecker wrote: > QuoVadis has applied to upgrade an existing root CA certificate for EV > use, as documented in the following bug: > > https://bugzilla.mozilla.org/show_bug.cgi?id=403665 > I have evaluated QuoVadis's request, as per the mozilla.org CA > certificate policy: > > http://

Re: window.crypto functions

Hi Bob, Robert Relyea wrote: > I think you need to be running a chrome to access this function > however;(. I don't think your average website can use it. If Firefox is considered an average and common browser than it's pretty usable. For MSIE we've got activeX (so I'm not the MS guy, don't ask

Re: window.crypto functions

Robert Relyea wrote: > > There are lots of APIs to get lots of data about smart cards, but just > like there are lots of APIs to do crypto, the aren't all available to > web designers through java script. Oh, it works excellent with Javascript in Firefox (and most derivatives I guess). Subrata

Re: SEC_ERROR_BAD_SIGNATURE with Firefox 3

Christophe Thiaux wrote: Hello, I can't connect on an ssl server with Firefox 3: it displays SEC_ERROR_BAD_SIGNATURE But if i'm connecting with Firefox 2 and accept the certificate definately, then the connexion with Firefox 3 works. Any idea of the problem ? Not from this sparse descrip

Re: window.crypto functions

Eddy Nigg (StartCom Ltd.) wrote: Subrata Mazumdar wrote: Eddy, I think that you can do it. Have you looked into nsIPK11Token interface (http://lxr.mozilla.org/mozilla1.8.0/source/security/manager/ssl/public/nsIPK11Token.idl) ? The nsIPK11Token interface would allow you to filter tokens bas

Re: window.crypto functions

Nelson Bolyard wrote: Robert Relyea wrote, On 2008-02-19 14:20: Eddy Nigg (StartCom Ltd.) wrote: Does anybody know if and which parameters might be obtained by the window.crypto functions and smart cards? For reference see this page: http://developer.mozilla.org/en/docs/JavaScript_cryp

SEC_ERROR_BAD_SIGNATURE with Firefox 3

Hello, I can't connect on an ssl server with Firefox 3: it displays SEC_ERROR_BAD_SIGNATURE But if i'm connecting with Firefox 2 and accept the certificate definately, then the connexion with Firefox 3 works. Any idea of the problem ? Thanks -- Chris ___