tree 9946d1ffecfd8a541fe75c1a8cbb8f3f5b0d4e2c
parent 598de5b6c8169b9d7222561a9270d89b2e4edac9
author Alfred Piccioni <alpic@google.com> 1692790123 +0200
committer Alfred Piccioni <alpic@google.com> 1692790940 +0000

Revert ntfs file context changes

Partial revert of:

commit 3e1dc57bf4f4aed2c117e2a743c59e3076f57338

commit 30ae427ed0d31fa883a6ba6e0d458efbac1394c8

The current file contexts could break potential implementations of NTFS
by partners in future. I am not rolling back the adjoining
fuseblkd_exec andfuseblkd_untrusted_exec code, because secure
implementations of fuseblk drivers should still endeavour to use the
more compartmentalised policies.

However, as we don't support NTFS officially, we should give
implementors the choices whether to use it or not, even if it will open
the door to potentially less secure implementations.

NTFS Context: http://b/254407246,
https://docs.google.com/document/d/1b5RjdhN2wFFqmLCK0P_chVyiEhiYqNlTn52TFBMNwxk

Bug: 294925212
Test: Builds and boot.
Change-Id: I6d3858517e797b3f7388f9d3f18dd4a11770d5bc