EditWYSIWYGAttach PDF Raw View►More Actions▼More Actions


Restore topic to revision: You will be able to review the topic before saving it to a new revision

Copy text and form data to a new topic (no attachments will be copied though).
Name of copy:
You will be able to review the copied topic before saving

Rename/move topic... scans links in all public webs (recommended)
Rename/move topic... scans links in CBI_ComputerSecurity web only
Delete topic... scans links in all public webs (recommended)
Delete topic... scans links in CBI_ComputerSecurity web only

Revision Date Username Comment
929 Dec 2015 - 18:11ThomasMisa 
803 Oct 2013 - 15:40norqu036? 
719 Apr 2013 - 11:26NicLewis 
619 Apr 2013 - 10:12NicLewis 
512 Mar 2013 - 10:19NicLewis 
405 Mar 2013 - 09:25NicLewis 
304 Mar 2013 - 11:24NicLewis 
225 Feb 2013 - 10:40NicLewis 
121 Feb 2013 - 09:23NicLewis 

Render style:     Context:


 History: r9 < r8 < r7 < r6 < r5
[X] Hide this message.
Notice: On June 30, 2016, UMWiki service will be decommissioned. If you have information in UMWIki that needs to be preserved, you should make plans to move it before that date. Google Sites is anticipated to be the most popular and appropriate alternative for users because it offers a more modern and user-friendly interface and unlimited capacity. To learn more about the features of Google Sites and other alternatives, and to identify which one best fits your needs, see the University’s Website Solution Selection Guide. If you have concerns or would like help regarding this change and your options, please contact Technology Help at help@umn.edu
You are here: UMWiki>CBI_ComputerSecurity Web>Systems>SystemsCAP (revision 7)

CAP

 

Becoming operational in 1976, the Cambridge CAP computer was the first computer to use successfully security capabilities in both hardware and software. Part of a project on memory protection at the University of Cambridge Computer laboratory between 1970 and 1977, the CAP computer ran a 32-bit processor, and a complete OS with a file system, and compilers. The CAP operating system used a process tree structure that featured a "Master coordinator," allowing each process to access the resources of its children without separate modes of operation. This meant that each process did not require special privileges or operating system intervention when addressing a linked subprocess. In practice, only two levels of this process hierarchy were used. An advantage of this system of process privilege control was its enhanced security of protected objects, while alleviating bottlenecks that would have occurred had each process been addressing the operating system for each system resource request.(1)

Additional Resources:

Notes

1 : lock Henry M. Levy, Compatibility-Based Computer Systems, (Digital Press, 1984), 79-83. (Log-in required)


Edit | WYSIWYG | Attach |  PDF |  History: r9 < r8 < r7 < r6 < r5 |  Backlinks |  Raw View | More topic actions...
Topic revision: r7 - 19 Apr 2013 - 11:26:43 - NicLewis
 
Signed in as lewi0740 (NicLewis) | Sign out
UMWiki UMWiki
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UMWiki? Send feedback