{"thread":{"id":"25642","subject":"certificate problem for *.github.com","startedAt":"2010-11-04T15:21:35Z","lastAt":"2010-11-04T15:46:00Z","messageCount":2,"participants":["Mattia Tomasoni","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"155172","messageId":"20101104162135.47chayboagwwkcc8@webmail.uu.se","threadId":"25642","inReplyTo":null,"subject":"certificate problem for *.github.com","fromName":"Mattia Tomasoni","fromEmail":"mattia.tomasoni.8371@student.uu.se","sentAt":"2010-11-04T15:21:35Z","receivedAt":"2010-11-04T15:21:35Z","isPatch":false,"sender":{"key":"mattia.tomasoni.8371@student.uu.se","avatar":null},"body":"Hello Git community!\nHere is my question: until a few days ago I used to be able to point  \nto a certain file in my git repository with the following url:\nhttp://github.com/percolator/percolator/raw/xml-1-1/src/xml/percolator_in.xsd\nNow this gets redirected to an https address.\nNo problem opening it with the browser; but I do get an error with,  \nfor instance, wget (...and, more important, with a program that  \nattempts to use that file as a schema against which some xml code is  \nvalidated...)\nI get:\ncertificate common name `*.github.com' doesn't match requested host  \nname `github.com'\n\nwget --no-check-certificate works...\n\nThank you!\nMattia\n"},{"id":"155174","messageId":"20101104154600.GA30026@sigill.intra.peff.net","threadId":"25642","inReplyTo":"20101104162135.47chayboagwwkcc8@webmail.uu.se","subject":"Re: certificate problem for *.github.com","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-11-04T15:46:00Z","receivedAt":"2010-11-04T15:46:00Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Nov 04, 2010 at 04:21:35PM +0100, Mattia Tomasoni wrote:\n\n> I get:\n> certificate common name `*.github.com' doesn't match requested host\n> name `github.com'\n> \n> wget --no-check-certificate works...\n\nThe problem is that wildcard names in certificates are not\nwell-specified. RFC 2818 leaves this particular case (matching\n\"*.domain\" to \"domain\") ambiguous:\n\n  Names may contain the wildcard character * which is considered to\n  match any single domain name component or component fragment. E.g.,\n  *.a.com matches foo.a.com but not bar.foo.a.com. f*.com matches\n  foo.com but not bar.com.\n\nRFC 2595 specifically outlaws it, but is talking about other non-HTTP\nprotocols (it is for TLS with IMAP, POP, and ACAP):\n\n  A \"*\" wildcard character MAY be used as the left-most name component\n  in the certificate.  For example, *.example.com would match\n  a.example.com, foo.example.com, etc. but would not match example.com.\n\nSo you can either send a bug report to wget to handle this case better,\nor you can complain to github not to use wildcard certificates in this\nway.\n\n-Peff\n"}]}