Ambient authority

From Erights

Revision as of 19:42, 11 June 2009 (view source) Kevin Reid (Talk | contribs) (use level 2 headings) ← Previous diff		Latest revision as of 23:43, 2 January 2011 (view source) Markm (Talk) (Correction suggested to me by Ben Laurie)
(12 intermediate revisions not shown)
Line 1:		Line 1:
-	== Draft Definition ==	+	The correct interpretation of this page relies on proper interpretation of words: [[subject, object, operation and permission]].
-	If a [[subject]] can [[operation on object|operate]] on all [[object]]s of a given type, we say that it has '''ambient authority'''.	+	== Definition ==
-	(Note: Dean Tribble and I (Mark S. Miller) are the coiners of the term "ambient authority". I have no idea what the above definition has to do with ambient authority. I am leaving it in place for now, with this note, in case it was a start on something that can be edited into something sensible. I have also changed the heading from "Definition" to "Draft Definition".)	+	IF a subject requests an action, typically by naming an object and an operation on that object, and the action is allowed because the subject has a permission that would allow the action, THEN we say that the subject has '''ambient authority'''.
-	== Comment ==	+	== Notes concerning the definition ==
-	Several access control models were invented and implemented to enable restriction of ambient authority of subjects. Many of them are:	+	Instead of "naming" an object, capability community often uses the term "designation" of an object.
-	* either weak (we cannot follow the [[POLA|principle of least authority]])	+
-	* or convoluted (it is hard to learn how to work with this model and be sure about [[authority]] of subjects).	+
-	Things become more "interesting" if we have to consider different security policies enforced via different alternative security mechanisms for the same type of objects and for different type of objects and the relevant transitivity relationship.	+
-	== Examples of ambient authority ==	+	Whether we can say that some chosen subject has '''ambient authority''' or not is solely determined by the fact HOW are operations allowed or denied. It is independent from the fact WHAT PERMISSIONS a given subject actually has. This matters in case of a term [[excess authority]].
-	If we consider UNIX processes run by some user as [[subject]]s and files owned by that user as [[object]]s then all processes have ''ambient authority'' to manipulate all those files.	+	The difference between [[ambient authority system]] and the [[designated authority system]] is that:
		+	* in the first case subjects, when they request some operation with some object, '''do not have to''' specify the permission that allows given operation with given object;
		+	* in the latter case subject, when they request some operation with some object, '''have to''' specify the permission this request with designated the permission that allows given operation with given object.
-	If we consider UNIX processes as [[subject]]s and TCP ports 1024--65535 as [[object]]s then all processes have ''ambient authority'' to listen to any TCP ports.	+	== See also ==
		+
		+	* [[Excess authority]]
		+	* [[Ambient authority system]]
		+
		+	== Examples of ambient authority ==
-	If we consider UNIX processes as [[subject]]s and UDP ports 1024--65535 as [[object]]s then all processes have ''ambient authority'' to listen to any UDP ports.	+	All UNIX processes run with some effective user id have ambient authority to manipulate all files accessible by that user id.
-	If we consider UNIX processes run by some user as [[subject]]s and all executable programs owned by that user as [[object]]s then all these processes have ''ambient authority'' to run any of those programs.	+	All UNIX processes have ''ambient authority'' to listen to TCP or UDP ports 1024--65535.
-	If we consider all functions defined in some C program as [[subject]]s and all functions in the same C program as [[object]]s then any function has ''ambient authority'' to call any other function (in C we can cast any integer to a function pointer and perform the call operation with this forged reference to a function).	+	All UNIX processes have ''ambient authority'' to send any signal to any other UNIX process.
-	If we consider all functions defined in some C program as [[subject]]s and all regions of the address space of the relevant process as [[object]]s then all these functions have ''ambient authority'' to read from or write to any such memory region.	+	== Acknowledgement ==
-	If we consider all processes in UNIX as [[subject]]s and also as [[object]]s then all UNIX processes have ''ambient authority'' to send any signal to any other process.	+	The term ''ambient authority'' was coined by Dean Tribble and Mark S. Miller.

---

Latest revision as of 23:43, 2 January 2011

The correct interpretation of this page relies on proper interpretation of words: subject, object, operation and permission.

Contents 1 Definition 2 Notes concerning the definition 3 See also 4 Examples of ambient authority 5 Acknowledgement

Definition

IF a subject requests an action, typically by naming an object and an operation on that object, and the action is allowed because the subject has a permission that would allow the action, THEN we say that the subject has ambient authority.

Notes concerning the definition

Instead of "naming" an object, capability community often uses the term "designation" of an object.

Whether we can say that some chosen subject has ambient authority or not is solely determined by the fact HOW are operations allowed or denied. It is independent from the fact WHAT PERMISSIONS a given subject actually has. This matters in case of a term excess authority.

The difference between ambient authority system and the designated authority system is that:

• in the first case subjects, when they request some operation with some object, do not have to specify the permission that allows given operation with given object;
• in the latter case subject, when they request some operation with some object, have to specify the permission this request with designated the permission that allows given operation with given object.

See also

• Excess authority
• Ambient authority system

Examples of ambient authority

All UNIX processes run with some effective user id have ambient authority to manipulate all files accessible by that user id.

All UNIX processes have ambient authority to listen to TCP or UDP ports 1024--65535.

All UNIX processes have ambient authority to send any signal to any other UNIX process.

Acknowledgement

The term ambient authority was coined by Dean Tribble and Mark S. Miller.