• Home
  • History
  • Annotate
  • only in /external/chromium_org/mojo/nacl/
NameDateSize

..12-Mar-201512 KiB

DEPS12-Mar-2015136

generator/12-Mar-20154 KiB

mojo_syscall.h12-Mar-2015310

mojo_syscall_internal.h12-Mar-20153.6 KiB

monacl_sel_main.cc12-Mar-20151.4 KiB

monacl_sel_main.h12-Mar-2015430

monacl_shell.cc12-Mar-2015775

README12-Mar-20151.1 KiB

README

1This is a prototype for plumbing Mojo into the NaCl sandbox.  It is
2currently insecure (see below), does not provide a stable ABI (IRT
3support must be added), and does not support Mojo functions that
4return pointers (for example, MojoMapBuffer).
5
6generator/interface.py contains a programmatic description of the
7stable Mojo interface.  This will need to be updated as the interface
8changes.  Run generator/generate_nacl_bindings.py to generate the
9bindings that plumb this interface into the NaCl sandbox.
10
11To test: Build "monacl_shell" and "monacl_test".  Run monacl_shell
12with the IRT as the first argument and the monacl_test as the second
13argument.  For example, to run a Debug 32-bit Intel build:
14
15  cd out/Debug
16  ./monacl_shell irt_core_newlib_x32.nexe monacl_test_newlib_x32.nexe
17
18Security TODO list:
19  Separate trusted and untrusted Mojo handles.
20  Validate and copy option structures.
21  Protect untrusted buffers passed into Mojo:
22    NaClVmIoWillStart/HasEnded.
23    volatile accesses to untrusted memory (untrusted code could race).
24  Overflow checking in array bounds validation.