Rethinking the filesystem as global mutable state, the root of all evil

Re:Rethinking the filesystem as global mutable state, the ro... by la_barba on Tuesday June 11, 2019 @02:17PM (#20158044)

You can prevent that by using the NX or the XD bit. Its a CPU feature and I believe the support was added over 15 years ago in most popular OSs. Here's the commit for Linux https://git.kernel.org/pub/scm/linux/kernel/git/history/hist...

>It's also pointless. If a program can cause damage by loading harmful code it can also cause damage directly.

It is not pointless, but it is also not perfect. That's why we have defense in depth. Where instead of having one perfect moat to protect the castle, you also have alligators and witches that turn people into frogs. :P

[ Parent | on HN ]

Re:Rethinking the filesystem as global mutable state, the ro... by anoncake on Wednesday June 12, 2019 @05:48AM (#20163084)

The OS can prevent it, but can it do so without making JIT impossible?

[ Parent | on HN ]

Re:Rethinking the filesystem as global mutable state, the ro... by andrekandre on Wednesday June 12, 2019 @03:38PM (#20168459)

well, if you can’t make pages executable you can “just in time” it by interpreting and writing it to an optimized interpreter format i suppose (but it will be much slower)... as an example, see WKWebView vs UIWebView (from iOS)

[ Parent | on HN ]

Re:Rethinking the filesystem as global mutable state, the ro... by anoncake on Thursday June 13, 2019 @01:57AM (#20172174)

You can do that but slow JIT kind of misses the point.

[ Parent | on HN ]