News for hackers. Stuff that matters.

A comment on Is WPA2 security broken due to Defcon MS-CHAPv2 cracking?. Parent comment

Re:Is WPA2 security broken due to Defcon MS-CHAPv2 cracking? by comex on Tuesday August 07, 2012 @04:54PM (#4352236)
Can't you get around that by just using a real domain name? There's no requirement that the server be accessible externally.
[ Parent | on HN ]
Re:Is WPA2 security broken due to Defcon MS-CHAPv2 cracking? by peterwwillis on Wednesday August 08, 2012 @10:02AM (#4355563)
There's no guarantee the CA won't revoke it if they find out you're using it for internal purposes.
[ Parent | on HN ]
Re:Is WPA2 security broken due to Defcon MS-CHAPv2 cracking? by comex on Wednesday August 08, 2012 @02:11PM (#4357064)
That makes no sense - there is no security problem with using a legitimate certificate for a real domain for internal purposes.

I haven't heard about these Baseline Requirements before your post, but http://www.cabforum.org/Baseline_Requirements_V1.pdf mentions 2015 but only in the context of reserved IPs and "Internal Server Names", which is defined as "A Server Name that is not resolvable using the public DNS". That makes more sense, because there is no way to say who owns such a domain.

Am I missing something?

[ Parent | on HN ]