Re:Ask HN: Why aren't Google, Facebook or Twitter CAs?
by PebblesHD on Thursday April 17, 2014 @07:17PM
(#7607130)
It would require a massive investment in infrastructure and licensing to become a CA that I suspect the major internet firms are unwilling to pay. The amount of paperwork and day to day management time required to run such an operation would be massive. In this case, unless the government/other certifying body is willing to accept current identifiers from these companies, they gain no benefit from becoming CAs.
[ Parent
| on HN ]
Re:Ask HN: Why aren't Google, Facebook or Twitter CAs?
by dragonwriter on Thursday April 17, 2014 @07:31PM
(#7607182)
> It would require a massive investment in infrastructure and licensing to become a CA that I suspect the major internet firms are unwilling to pay.
Or they could just invest some of the vast pile of cash that some of them (I'm looking at you, Google) have lying around, and buy an existing, widely trusted CA, which would probably be lower-risk than investing in infrastructure and licensing; they still end up with full control of how the CA works going forward either way.
Re:Ask HN: Why aren't Google, Facebook or Twitter CAs?
by dfc on Thursday April 17, 2014 @07:33PM
(#7607193)
Why do you think it would be lower risk?
Re:Ask HN: Why aren't Google, Facebook or Twitter CAs?
by dragonwriter on Thursday April 17, 2014 @07:43PM
(#7607231)
> Why do you think it would be lower risk?
Because gaining control of an existing trusted CAs (and, consequently, existing widely trusted root certificates) gives them built-in reach that doesn't have to be be grown.
Re:Ask HN: Why aren't Google, Facebook or Twitter CAs?
by niels_olson on Thursday April 17, 2014 @07:51PM
(#7607251)
I don't see how paperwork is ever an issue for something as far-reaching as Google.
What licensing is involved? How is the day-to-day management even a thing? Didn't Shuttleworth make his money this way?
I would think a graph-backed cert would be an ideal way to authenticate service providers.