On Fri, Jun 18, 2004 at 06:14:41AM -0700, Lev Walkin wrote:
Gisle Vanem wrote:
Lev Walkin [EMAIL PROTECTED] said:
No, fnmatch() is fairly portable across Unixes though.
Please note that fnmatch() use is against RFC2818.
Please explain why.
Because *.domain.com shouldn't match
Lev Walkin [EMAIL PROTECTED] said:
No, fnmatch() is fairly portable across Unixes though.
Please note that fnmatch() use is against RFC2818.
Please explain why.
--gv
__
OpenSSL Project
Gisle Vanem wrote:
Lev Walkin [EMAIL PROTECTED] said:
No, fnmatch() is fairly portable across Unixes though.
Please note that fnmatch() use is against RFC2818.
Please explain why.
Because *.domain.com shouldn't match abc.def.ghi.domain.com
per RFC2818#3.1, as it does with fnmatch().
However,
Joe Orton wrote:
On Sat, Jun 12, 2004 at 07:38:42PM +0200, Gisle Vanem wrote:
How is the /CN= supposed to be encoded for a host/domain-
name using international characters? In some specified charset
(utf8?) or in the ASCII Compatible Encoded form?
I ask since in an application here (using libidn),
On Sat, Jun 12, 2004 at 07:38:42PM +0200, Gisle Vanem wrote:
How is the /CN= supposed to be encoded for a host/domain-
name using international characters? In some specified charset
(utf8?) or in the ASCII Compatible Encoded form?
I ask since in an application here (using libidn), I get the
On Mon, Jun 14, 2004 at 12:11:33PM -0400, Jeffrey Altman wrote:
What follows is simply my opinion but I believe it to be correct:
The name must match the text the user entered when specifying the
desired host. As such there are multiple input forms which resolve to
the same name. Instead of
What follows is simply my opinion but I believe it to be correct:
The name must match the text the user entered when specifying the
desired host.
As such there are multiple input forms which resolve to the same name.
Instead of
using Common Name you should use subjectAltName and provide two
