Device Driver Access Control #3635
Labels
area: Kernel
Enhancement
Changes/Updates/Additions to existing features
priority: medium
Medium impact/importance bug
Milestone
Reported by Andrew Boie:
For memory protection we want to selectively grant threads access to device driver APIs, all-or-nothing may be too coarse for security concerns. However, it may not be feasible to implement this on all arches, as some MPU-based systems may have too few available regions to do this properly. Design an optional access control mechanism and APIs such that a thread can designate what drivers or subsystems it has access to before it drops supervisor privileges.
(Imported from Jira ZEP-2197)
The text was updated successfully, but these errors were encountered: