Memoryless subsystems Export

@article{Fenton1974, abstract = {A memoryless subsystem is incapable of communicating unauthorised information about data input to the outside world. Such systems are important in the study of protection systems, but are difficult to implement. This paper derives a model of such a system and further gives a proof of its correctness. 10.1093/comjnl/17.2.143}, author = {Fenton, J. S.}, citeulike-article-id = {3390829}, citeulike-linkout-0 = {http://dx.doi.org/10.1093/comjnl/17.2.143}, citeulike-linkout-1 = {http://comjnl.oxfordjournals.org/cgi/content/abstract/17/2/143}, comment = {Computer hardware support for running secure software that can't store information about what it has done. Instead of designating areas of memory (by address) that should be protected, the approach in this paper is to associate the the data with a protection level "mark" so that private/secure data can't be accessed by non-secure code. Introduced me to the Minksy machine. }, day = {1}, doi = {10.1093/comjnl/17.2.143}, journal = {The Computer Journal}, keywords = {architecture, computer-science, hardware, have-paper-copy, interesting-rating--3, not-related-to-engd, security}, month = {February}, number = {2}, pages = {143--147}, posted-at = {2008-10-09 15:03:13}, priority = {0}, title = {Memoryless subsystems}, url = {http://dx.doi.org/10.1093/comjnl/17.2.143}, volume = {17}, year = {1974} }

TY - JOUR ID - Fenton1974 L3 - citeulike-article-id:3390829 N2 - A memoryless subsystem is incapable of communicating unauthorised information about data input to the outside world. Such systems are important in the study of protection systems, but are difficult to implement. This paper derives a model of such a system and further gives a proof of its correctness. 10.1093/comjnl/17.2.143 IS - 2 JF - The Computer Journal EP - 147 TI - Memoryless subsystems VL - 17 SP - 143 KW - architecture KW - computer-science KW - hardware KW - have-paper-copy KW - interesting-rating--3 KW - not-related-to-engd KW - security N1 - Computer hardware support for running secure software that can't store information about what it has done. Instead of designating areas of memory (by address) that should be protected, the approach in this paper is to associate the the data with a protection level "mark" so that private/secure data can't be accessed by non-secure code. Introduced me to the Minksy machine. AU - Fenton, JS PY - 1974/02/01/ UR - http://dx.doi.org/10.1093/comjnl/17.2.143 ER -