2 ms·
I think he forgot to write part where he explains why native client is better than ActiveX, or did I just overlook it? Anyway, he seems to have a very specific
by Tichy 17y ago
I think he forgot to write part where he explains why native client is better than ActiveX, or did I just overlook it?
Anyway, he seems to have a very specific, narrow use case (native client).
- by 17y agoIt's explained better on the Wikipedia page http://en.wikipedia.org/wiki/Google_Native_Client http://en.wikipedia.org/wiki/Google_Native_Client It seems to be sandboxed, whereas ActiveX is a security nightmare.
- Tichy 17y agoI am pretty sure ActiveX had some kind of sandbox model as well? Even so, I remain very skeptic about this.
- djcapelis 17y agoThere's "sandboxes" and then there's sandboxes. Native Client uses the latter while ActiveX had barely the former. It does present a real concern and exposing additional APIs is going to always present increased security risk. That said, having looked a bit at Native Client's sandbox and having examined the findings of the well respected security researchers who examined the sandbox protections, Google's taking a pretty good whack at it and their sandbox itself is fairly sound. My worry is not with their sandbox, but the additional APIs that they expose with it. (See also: WebGL which now throws your entire GL stack into your web browser as security critical code.)
- gmartres 17y agoBecause ActiveX is a proprietary, Windows-only technology?
- Tichy 17y agoOK, I was thinking in the security sense, but of course broader availability is interesting.