Filesystem

From Adam Colton
Revision as of 17:36, 23 September 2019 by Adamcolton (talk | contribs) (Created page with "Directly accessing the filesystem triggers a security elevation. However, we can include a filesystem interface that can be accessed without the security elevation. The inter...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Directly accessing the filesystem triggers a security elevation. However, we can include a filesystem interface that can be accessed without the security elevation.

The interface version is useful. First - it means that a library cannot secretly access the filesystem, it has to request access. Second, we can create a virtual filesystem to sandbox an application. The sandbox can even be persistened. We can also add alerts so that if a library tries to do something suspicious (like accessing os files), we can track it.

We can also create an intermediary that does allow direct access to the filesystem but limits what files and directories are shown.