Michael Ströder wrote:
>
> Massimiliano Pala wrote:
> >
> > Dr Stephen Henson wrote:
> >
> > > Oh and don't even think about using BMPStrings or UTF8Strings in
> > > certificates or CRLs BTW.
> >
> > Do you, or anyone, have contacts with Netscape people (or can get me
> > in contact with) to know
Massimiliano Pala wrote:
>
> Dr Stephen Henson wrote:
>
> > Oh and don't even think about using BMPStrings or UTF8Strings in
> > certificates or CRLs BTW.
>
> Do you, or anyone, have contacts with Netscape people (or can get me
> in contact with) to know what they are doing by now and if they w
Dr Stephen Henson wrote:
> Oh and don't even think about using BMPStrings or UTF8Strings in
> certificates or CRLs BTW.
Do you, or anyone, have contacts with Netscape people (or can get me
in contact with) to know what they are doing by now and if they will
or plan to correct thoose bugs/unfeatu
Massimiliano Pala wrote:
>
>
> So, what I have to do ?? I do have to set the CA subject to something like:
>
> CN=CA Operator, O=OpenCA, C=IT
>
Yes that ought to do it.
> Another question: as far as I know Netscape likes only v1 CRLs (without
> extentions... is that true ???
>
Wel
Dr Stephen Henson wrote:
> Yes it is known. Its caused by importing a CRL without a commonName (CN)
> field. The only way to undo the crash (other than working out which
> records got added to the database and manually deleting them) is to
> delete the key and certificate database and restart wit
Massimiliano Pala wrote:
>
> Hi,
>
> I am experiencing a Netscape CRASH when, after successfully importing
> the CRL, I want to view the CRL... simply go to:
>
> Security -> Signers -> View/Edit CRLs
>
> Netscape Crashes! It could be simply because the CRL was issued by a
> CA with 204
Hi,
I am experiencing a Netscape CRASH when, after successfully importing
the CRL, I want to view the CRL... simply go to:
Security -> Signers -> View/Edit CRLs
Netscape Crashes! It could be simply because the CRL was issued by a
CA with 2048bit key ??? It is a known Nescape bug ??
I a
