Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by gcv on Friday August 12, 2011 @12:41AM
(#2875999)
Could someone more familiar with the effort comment on whether Google realistically solved the security and trust problems inherent in the approach? I'm assuming that
is somehow blocked, but native code is a bonanza of attack vectors.
[ Parent
| on HN ]
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by krasin on Friday August 12, 2011 @12:46AM
(#2876011)
fork is not available under NaCl
http://code.google.com/p/nativeclient/issues/detail?id=1239
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by xtacy on Friday August 12, 2011 @12:47AM
(#2876014)
The Native Client paper[1] was published in 2009. The main reason it took so long to be officially released is that it underwent a lot of scrutiny by various security researchers[2], through the Google bounty program. In fact, NaCl has been shipping with Chrome all along; it just needed a flag to enable it (--enable-nacl).
You should read their research paper for interesting insights.
[1] http://www.chromium.org/nativeclient/reference/research-pape...