Scheduler-independent declassification
From MaRDI portal
Recommendations
Cites work
- Controlling the What and Where of Declassification in Language-Based Security
- Downgrading policies and relaxed noninterference
- Non-interference through determinism
- Paralocks, role-based information flow control and beyond
- Programming Languages and Systems
- Programming Languages and Systems
- Securing interaction between threads and the scheduler in the presence of synchronization
- The Shadow Knows: Refinement of Ignorance in Sequential Programs
- Who Can Declassify?
Cited in
(5)- Automated enforcement for relaxed information release with reference points
- Robust declassification by incremental typing
- Who Can Declassify?
- Linear Declassification
- A Formalization of Declassification with WHAT-and-WHERE-Security
This page was built for publication: Scheduler-independent declassification
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q2908558)