Scribd
Upload
26 views

CH 18

This document discusses operating system protection mechanisms. It covers goals of protection like ensuring objects are only accessed by allowed processes. Access is controlled using domains that define access rights for objects. An access matrix models the protection by defining the operations each domain can perform on objects. Implementation involves access control lists and capability lists. Rights can be revoked by modifying these lists. Capability systems and language-based approaches are also discussed.

Uploaded by

Jaohar Islam Dudaeb Sagar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
26 views

CH 18

This document discusses operating system protection mechanisms. It covers goals of protection like ensuring objects are only accessed by allowed processes. Access is controlled using domains that define access rights for objects. An access matrix models the protection by defining the operations each domain can perform on objects. Implementation involves access control lists and capability lists. Rights can be revoked by modifying these lists. Capability systems and language-based approaches are also discussed.

Uploaded by

Jaohar Islam Dudaeb Sagar
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 19

Module 18: Protection

 Goals of Protection
 Domain of Protection
 Access Matrix
 Implementation of Access Matrix
 Revocation of Access Rights
 Capability-Based Systems
 Language-Based Protection

Operating System Concepts 18.1 Silberschatz, Galvin and Gagne 2002


Protection

 Operating system consists of a collection of objects,


hardware or software

 Each object has a unique name and can be accessed


through a well-defined set of operations.

 Protection problem - ensure that each object is accessed


correctly and only by those processes that are allowed to
do so.

Operating System Concepts 18.2 Silberschatz, Galvin and Gagne 2002


Domain Structure

 Access-right = <object-name, rights-set>


where rights-set is a subset of all valid operations that
can be performed on the object.

 Domain = set of access-rights

Operating System Concepts 18.3 Silberschatz, Galvin and Gagne 2002


Domain Implementation (UNIX)

 System consists of 2 domains:


 User
 Supervisor

 UNIX
 Domain = user-id
 Domain switch accomplished via file system.
 Each file has associated with it a domain bit (setuid bit).
 When file is executed and setuid = on, then user-id is
set to owner of the file being executed. When execution
completes user-id is reset.

Operating System Concepts 18.4 Silberschatz, Galvin and Gagne 2002


Domain Implementation (Multics)

 Let Di and Dj be any two domain rings.


 If j < I  Di  Dj

Multics Rings
Operating System Concepts 18.5 Silberschatz, Galvin and Gagne 2002
Access Matrix

 View protection as a matrix (access matrix)

 Rows represent domains

 Columns represent objects

 Access(i, j) is the set of operations that a process


executing in Domaini can invoke on Objectj

Operating System Concepts 18.6 Silberschatz, Galvin and Gagne 2002


Access Matrix

Figure A

Operating System Concepts 18.7 Silberschatz, Galvin and Gagne 2002


Use of Access Matrix

 If a process in Domain Di tries to do “op” on object Oj,


then “op” must be in the access matrix.

 Can be expanded to dynamic protection.


 Operations to add, delete access rights.
 Special access rights:
 owner of Oi
 copy op from Oi to Oj
 control – Di can modify Dj access rights
 transfer – switch from domain Di to Dj

Operating System Concepts 18.8 Silberschatz, Galvin and Gagne 2002


Use of Access Matrix (Cont.)

 Access matrix design separates mechanism from policy.


 Mechanism
 Operating system provides access-matrix + rules.
 If ensures that the matrix is only manipulated by
authorized agents and that rules are strictly enforced.
 Policy
 User dictates policy.
 Who can access what object and in what mode.

Operating System Concepts 18.9 Silberschatz, Galvin and Gagne 2002


Implementation of Access Matrix

 Each column = Access-control list for one object


Defines who can perform what operation.

Domain 1 = Read, Write


Domain 2 = Read
Domain 3 = Read


 Each Row = Capability List (like a key)
Fore each domain, what operations allowed on what objects.
Object 1 – Read
Object 4 – Read, Write, Execute
Object 5 – Read, Write, Delete, Copy

Operating System Concepts 18.10 Silberschatz, Galvin and Gagne 2002


Access Matrix of Figure A With Domains as Objects

Figure B

Operating System Concepts 18.11 Silberschatz, Galvin and Gagne 2002


Access Matrix with Copy Rights

Operating System Concepts 18.12 Silberschatz, Galvin and Gagne 2002


Access Matrix With Owner Rights

Operating System Concepts 18.13 Silberschatz, Galvin and Gagne 2002


Modified Access Matrix of Figure B

Operating System Concepts 18.14 Silberschatz, Galvin and Gagne 2002


Revocation of Access Rights

 Access List – Delete access rights from access list.


 Simple
 Immediate

 Capability List – Scheme required to locate capability in


the system before capability can be revoked.
 Reacquisition
 Back-pointers
 Indirection
 Keys

Operating System Concepts 18.15 Silberschatz, Galvin and Gagne 2002


Capability-Based Systems

 Hydra
 Fixed set of access rights known to and interpreted by the
system.
 Interpretation of user-defined rights performed solely by
user's program; system provides access protection for use
of these rights.

 Cambridge CAP System


 Data capability - provides standard read, write, execute of
individual storage segments associated with object.
 Software capability -interpretation left to the subsystem,
through its protected procedures.

Operating System Concepts 18.16 Silberschatz, Galvin and Gagne 2002


Language-Based Protection

 Specification of protection in a programming language


allows the high-level description of policies for the
allocation and use of resources.

 Language implementation can provide software for


protection enforcement when automatic hardware-
supported checking is unavailable.

 Interpret protection specifications to generate calls on


whatever protection system is provided by the hardware
and the operating system.

Operating System Concepts 18.17 Silberschatz, Galvin and Gagne 2002


Protection in Java 2

 Protection is handled by the Java Virtual Machine (JVM)

 A class is assigned a protection domain when it is loaded


by the JVM.

 The protection domain indicates what operations the


class can (and cannot) perform.

 If a library method is invoked that performs a privileged


operation, the stack is inspected to ensure the operation
can be performed by the library.

Operating System Concepts 18.18 Silberschatz, Galvin and Gagne 2002


Stack Inspection

Operating System Concepts 18.19 Silberschatz, Galvin and Gagne 2002

You might also like