Restrict access to files to signed code

Restricting access to files to signed code is method to improve security by limiting code that can read, write or have full access to a given file.

This is a ticket is discusses this feature in more detail:

• Would restricting access to files be a useful?
• What level of sophistication would be required?
  1. Sufficient to simple restrict all access to signed code only?
  2. Access restriction to specified files only?
  3. Different gpg signatures to access different files?
  4. Ability to specify Read access only or full access?
• How would superfiles be treated?
  1. If superfile access is restricted, can individual component parts be accessed?
  2. If restriction is specified for an individual part of a superfile, would that restriction need to propogate to the super file
  3. Where would the restriction be enabled/specified? Dali?
  4. How would access restriction be maintained when accessed outside Thor: for example, through EclWatch, file spraying/despraying, various std.File operations?
• If signed file access restriction was available, how likely is it to be used?