We recently upgraded from 0.4.12 to 0.8.14 (about freaking time, huh?)
and our SSL certificate checking is having some troubles with some
CAs.
We're receiving the following error when we test for 'authorized'.
"Hostname/IP doesn't match certificate's altnames"
Here's the pertinent code to reprodu
On Thu, Nov 8, 2012 at 5:38 PM, Shawn Parrish wrote:
> We recently upgraded from 0.4.12 to 0.8.14 (about freaking time, huh?)
> and our SSL certificate checking is having some troubles with some
> CAs.
> We're receiving the following error when we test for 'authorized'.
>
> "Hostname/IP doesn't ma
We thought that might be the case but the checks work fine in 0.4.12,
are seen as valid by all major browsers as well as curl, like you
said. Some Thawte certs which I believe are valid are also failing
with this error message.
I'm pretty sure the error is incorrect as the hostname matches.
Any
On Thu, Nov 8, 2012 at 6:28 PM, Shawn Parrish wrote:
> We thought that might be the case but the checks work fine in 0.4.12,
> are seen as valid by all major browsers as well as curl, like you
> said. Some Thawte certs which I believe are valid are also failing
> with this error message.
>
> I'm
On Thu, Nov 8, 2012 at 10:34 AM, Ben Noordhuis wrote:
> On Thu, Nov 8, 2012 at 6:28 PM, Shawn Parrish wrote:
>> We thought that might be the case but the checks work fine in 0.4.12,
>> are seen as valid by all major browsers as well as curl, like you
>> said. Some Thawte certs which I believe ar
