3 ms·
Could someone more familiar with the effort comment on whether Google realistically solved the security and trust problems inherent in the approach? I'm assumin
by gcv 15y ago
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
while(1) fork();
is somehow blocked, but native code is a bonanza of attack vectors.
- krasin 15y agofork is not available under NaCl http://code.google.com/p/nativeclient/issues/detail?id=1239 http://code.google.com/p/nativeclient/issues/detail?id=1239
- xtacy 15y agoThe 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-papers http://www.chromium.org/nativeclient/reference/research-pape... [2] http://code.google.com/contests/nativeclient-security/ http://code.google.com/contests/nativeclient-security/