[ipxe-devel] Wildcard HTTPS cert support.

Nicolas Sylvain nsylvain at gmail.com
Fri Sep 6 15:53:25 UTC 2013

>From http://tools.ietf.org/html/rfc2818 I see "

Names may contain the wildcard character * which is considered to match any
single domain name component or component fragment. E.g., *.a.com matches
foo.a.com but not bar.foo.a.com. f*.com matches foo.com but not bar.com.

I'm clearly not an HTTPS expert, but I'm not aware of any more rules. If it
makes sense to you as well I can fix my patch to implement it. (unless
someone else has a better patch already).



On Fri, Sep 6, 2013 at 8:30 AM, Michael Brown <mbrown at fensystems.co.uk>wrote:

> On 28/08/13 22:50, Nicolas Sylvain wrote:
>> I made a small change to actually add basic wildcard support to get
>> unstuck.   It only works for cases like this one (leading wildcard).
> Happy to accept a general-purpose patch which applies the wildcard
> matching rules as defined by the RFC, if anyone wants to write one.
> Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130906/d1a11157/attachment.htm>

More information about the ipxe-devel mailing list