4 ms·
As part of the new Baseline Requirements for public CAs, certificate authorities are not able to issue certificates for internal purposes after 2015. This mean
by peterwwillis 14y ago
As part of the new Baseline Requirements for public CAs, certificate authorities are not able to issue certificates for internal purposes after 2015.
This means that your client will have to have the certificate installed on it prior to authentication. So a random person connecting to your AP may be subject to an untrusted certificate, or require manual installation before connecting.
So.... in 2015, we might be fucked.
- apendleton 14y agoThis article assumes self-signed certs anyway, and specifically addresses procedures for disseminating them.
- peterwwillis 14y agoThe article mentions how to work with self-signed certs, but that is not the point. Many orgs don't run their own root CA because the cost of supporting all the devices just to auth securely is overwhelming, and just buying one cert from VeriSign is enough to keep it secure. Except when 2015 rolls around. If you maintain wireless networks for large enterprises, it's kind of a big deal.
- comex 14y agoCan't you get around that by just using a real domain name? There's no requirement that the server be accessible externally.
- peterwwillis 14y agoThere's no guarantee the CA won't revoke it if they find out you're using it for internal purposes.
- comex 14y agoThat 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 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?