Hi,
> so in fact I tried with NS v2.0, 3.0 , MSIE 4.0 5.0, and it works fine with a
> slf signed certificate . The only software which doesn't run with it is NS 4.06
> and latter versions.
> So what is the problem is the below solution is the right way ?
I had a similar problem to this last
On Fri, Apr 30, 1999 at 11:28:45AM +0100, Anthony Peacock wrote:
> It turns out the Netscape v4.06 or higher, requires that the CN (common
> name) of the certificate matches the DNS name of the server. I think this
> _is_ part of the standard, it is just that the other browsers don't complain.
Hi,
yes I think too, but I tried it the problem I think it's I have my apache
server installed on port 4440, so my CN should be secure.mydomain.com:4440, but
this doesn't operate. Is it that the problem ?
Best regards
Emmanuel Poitier
On Fri, 30 Apr 1999, you wrote:
>Hi,
>
>> so in fact I
> On Fri, Apr 30, 1999 at 11:28:45AM +0100, Anthony Peacock wrote:
>
> > It turns out the Netscape v4.06 or higher, requires that the CN (common
> > name) of the certificate matches the DNS name of the server. I think this
> > _is_ part of the standard, it is just that the other browsers don't
> Hi,
>
> yes I think too, but I tried it the problem I think it's I have my apache
> server installed on port 4440, so my CN should be secure.mydomain.com:4440, but
> this doesn't operate. Is it that the problem ?
It might be that your problem is different to mine, because I don't put the
Hi,
so in fact I tried with NS v2.0, 3.0 , MSIE 4.0 5.0, and it works fine with a
slf signed certificate . The only software which doesn't run with it is NS 4.06
and latter versions.
So what is the problem is the below solution is the right way ?
Thanks,
Emmanuel Poitier
On Thu, 29 Apr 199
Emmanuel wrote:
> the problem I think it's I have my apache
> server installed on port 4440, so my CN should be
> secure.mydomain.com:4440, but
> this doesn't operate. Is it that the problem ?
Wrong. CN shoud be FQDN of your server (w/o service).
In your case: CN=secure.mydomain.com
Regards,
