Lines Matching refs:labels

65 Smack uses extended attributes (xattrs) to store labels on filesystem
233 	This contains labels processes must have for CAP_MAC_ADMIN
236 	label. The values are set by writing the desired labels, separated
244 	    only allowed when subject's and object's labels are equal.
259 	This interface contains a list of labels to which the process can
263 	CAP_MAC_ADMIN to relabel itself to one of labels from predefined list.
266 	The values are set by writing the desired labels, separated
365 on what subjects can access which objects, based on the labels attached to
370 Smack labels are ASCII character strings. They can be up to 255 characters
372 Single character labels using special characters, that being anything
374 team. Smack labels are unstructured, case sensitive, and the only operation
375 ever performed on them is comparison for equality. Smack labels cannot
378 Smack labels cannot begin with a '-'. This is reserved for special options.
380 There are some predefined labels:
423 different labels is desired. One example is the familiar spy model of
427 mechanism for specifying rules allowing access between labels.
465 Spaces are not allowed in labels. Since a subject always has access to files
495 for two processes with different labels to share data without granting
507 tasks with identical Smack labels and requires no access checks.
518 immediately. For any pair of subject and object labels there can be only
557 label values to match the Smack labels being used without administrative
590 The mapping of Smack labels to CIPSO values is defined by writing to
666 to processes running with various labels.
670 Smack maintains labels on file system objects using extended attributes. The
714 	all labels set on the filesystem. Not yet enforced.
716 	smackfsfloor=label: specifies a label to which all labels set on the