3 ms·
The problem is really _naming_ these devices first of all. If they have (global) names there's no problem to issue a certificate for those names. But so often
by tialaramex 8y ago
The problem is really _naming_ these devices first of all. If they have (global) names there's no problem to issue a certificate for those names.
But so often the device doesn't have any name at all, so it's maybe 10.0.0.1, and so is everything else, the problem only appears to be in the security layer because that's the first place which absolutely insists that you can't have a situation where everybody is just named "Bruce" with no other identifier.
Where it does have a name, the name is often not part of the global namespace. At least here we can fix that with a namespace suffix. Sold five million routers with serial numbers? Name them $serialnumber.routers.your-company.example and problem solved. Now that they have a name, issuing them certificates isn't difficult.
(Yes, a commercial vendor who'll hook you up with five million certificates won't do it for free. The little rubber feet and the half-arsed English translation of the instruction manual weren't free either. Too bad)
- stefan_ 8y agoThat assumes your DNS is running through the device itself. For a router, maybe, beyond that, not really.