Re:Enhancing digital certificate security (Fake *.Google.com...
by gravitronic on Thursday January 03, 2013 @03:27PM
(#5004454)
Can you elaborate why you've spent the considerable time to do this? Do you habitually travel / connect to completely nefarious networks?
[ Parent
| on HN ]
Re:Enhancing digital certificate security (Fake *.Google.com...
by jrabone on Thursday January 03, 2013 @03:58PM
(#5004613)
Much for the same reasons I run my own mail server - because I can, I learned something doing it, it gives me more control than I'd otherwise have. I also don't trust any network with plain-text credentials so TLS was a requirement for mobile email.
IronKey was something I already used, so it was natural to try and build a minimal CA that fit on it.
Given the choice I'd prefer a good VPN solution but the aforementioned pre-smartphones simply couldn't do that and SSL VPNs weren't common, so TLS was what we had. Now, that little CA primarily gets used for generating Xauth-RSA certificates for my IPSEC VPNs...
Re:Enhancing digital certificate security (Fake *.Google.com...
by newman314 on Friday January 04, 2013 @05:29AM
(#5007050)
Any chance you could release a scrubbed setup or a blog post?
I'm looking at doing this and rather not have to slog through the nuances if possible. (I deal with certain on a sufficiently infrequent basis that I have to actively try to figure the steps again. One of the frustrating things of having to deal with cryptic options)
Re:Enhancing digital certificate security (Fake *.Google.com...
by gravitronic on Thursday January 03, 2013 @10:21PM
(#5006104)
neat, thanks for the followup!