2009 30th IEEE Symposium on Security and Privacy 2009
DOI: 10.1109/sp.2009.25
|View full text |Cite
|
Sign up to set email alerts
|

Native Client: A Sandbox for Portable, Untrusted x86 Native Code

Abstract: This paper describes the design, implementation and evaluation of Native Client, a sandbox for untrusted x86 native code. Native Client aims to give browser-based applications the computational performance of native applications without compromising safety. Native Client uses software fault isolation and a secure runtime to direct system interaction and side effects through interfaces managed by Native Client. Native Client provides operating system portability for binary code while supporting performance-orie… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

1
374
0
2

Year Published

2012
2012
2018
2018

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 452 publications
(393 citation statements)
references
References 24 publications
1
374
0
2
Order By: Relevance
“…Enforcement of usage control requirements has been done at the OS level [26,27,3], at the X11 level [4], for Java [11,12,28], the .NET CIL [13] and machine languages [14,15,29]; at the level of an enterprise service bus [16]; for dedicated applications such as the Internet Explorer [17] and in the context of digital rights management [18][19][20]. These solutions focus on one of the two aspects of the problem: either data flow tracking or event-driven usage control.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Enforcement of usage control requirements has been done at the OS level [26,27,3], at the X11 level [4], for Java [11,12,28], the .NET CIL [13] and machine languages [14,15,29]; at the level of an enterprise service bus [16]; for dedicated applications such as the Internet Explorer [17] and in the context of digital rights management [18][19][20]. These solutions focus on one of the two aspects of the problem: either data flow tracking or event-driven usage control.…”
Section: Related Workmentioning
confidence: 99%
“…opened, (lines 12-15) at most 4 further times and within 30 seconds (1 timestep = 1 second) after the first use (lines [8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27]; further attempts of opening the file will result in opening a predefined error message (lines 28-34).…”
Section: B1 Operating Systemmentioning
confidence: 99%
See 1 more Smart Citation
“…To mitigate the threats from dynamic libraries, a range of solutions have been proposed to isolate program components to control their privilege [5,6,16,18]. Most solutions adopt a separated memory model: a component can only access its own memory, which is mutually exclusive with the memory of the main program.…”
Section: Introductionmentioning
confidence: 99%
“…We use NativeClient (NaCl) [18] as an example to illustrate the need for a transparent library security mechanism. NaCl is designed for isolating untrusted native browser plugins.…”
Section: Introductionmentioning
confidence: 99%