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 other ideas?
On Thu, Nov 8, 2012 at 9:47 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> On Thu, Nov 8, 2012 at 5:38 PM, Shawn Parrish <sparr...@nodeping.com> 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
>> 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 reproduce.
>> var tls = require('tls');
>> We're seeing this with some digicert and some thawte certs so far.
>> Anything change in the CA handling or checkServerIdentity function of
> I guess it's to be expected. Here is what `openssl s_client
> AFAIK, all of DigiCert's signing authority has been revoked so it's no
> It *is* rather peculiar that the curl on my system accepts it just
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.