4 ms·
I wonder how many people had to approve the decision to send publicly trusted private keys to users. It seems like such an obvious security mistake that I didn'
by adrianN 9y ago
I wonder how many people had to approve the decision to send publicly trusted private keys to users. It seems like such an obvious security mistake that I didn't think people would make it.
- tehlike 9y agoI am more interested in how does an embedded app get the cert in the first place. That cert should be accessed by automation and restricted to a set of people only.
- pm90 9y agoI can easily see it as being a "stop gap" solution to get a deadlined proof of concept working, and then some other team getting assigned to take the POC to production and not being smart enough to remedy a very obvious security hole.
- rrobukef 9y agoIt's automatically embedded by the build script ;)
- tehlike 9y agolol, yes, except the acl is wrong :)
- noahdesu 9y agoHow do security procedures for handling, distributing, and revoking keys work in practice, especially at big companies that release a lot of software? For some companies getting this right would have to be critical, but I would be nervous if everything hinged on keeping a small 4K private key file secure.
- theossuary 9y agoWell then you should be very nervous, most of the internet's security is centered around keeping 4kb files secure.
- icedchai 9y agoIf you read that thread or do a DNS lookup, it turns out drmlocal.cisco.com points to 127.0.0.1. I wonder what they're actually using it for...
- stereo 9y agoProbably communication with the browser over a kind of web API.
- peterwwillis 9y agoIIRC, with many CAs all you have to do to generate a trusted certificate is show you control a subdomain. Once you control the subdomain, you get your cert signed by a CA, and then you can send keys anywhere you want. In terms of who was _supposed_ to approve the decision, there is a policy in place for that. Did they get that approval? Who knows, but I think in theory there isn't a mechanism to enforce it once you control the subdomain. Never underestimate the potential to make security mistakes.