Lines Matching full:labels

77 Smack uses extended attributes (xattrs) to store labels on filesystem
228 	specify read and execute access. Labels are limited to 23
282 	This contains labels processes must have for CAP_MAC_ADMIN
285 	label. The values are set by writing the desired labels, separated
298 	    only allowed when subject's and object's labels are equal.
318 	This interface contains a list of labels to which the process can
322 	``CAP_MAC_ADMIN`` to relabel itself to one of labels from predefined list.
325 	The values are set by writing the desired labels, separated
435 on what subjects can access which objects, based on the labels attached to
438 Labels  section in Smack Basics
441 Smack labels are ASCII character strings. They can be up to 255 characters
443 Single character labels using special characters, that being anything
445 team. Smack labels are unstructured, case sensitive, and the only operation
446 ever performed on them is comparison for equality. Smack labels cannot
449 Smack labels cannot begin with a '-'. This is reserved for special options.
451 There are some predefined labels::
499 different labels is desired. One example is the familiar spy model of
503 mechanism for specifying rules allowing access between labels.
542 Spaces are not allowed in labels. Since a subject always has access to files
573 for two processes with different labels to share data without granting
585 tasks with identical Smack labels and requires no access checks.
597 immediately. For any pair of subject and object labels there can be only
646 label values to match the Smack labels being used without administrative
679 The mapping of Smack labels to CIPSO values is defined by writing to
771 to processes running with various labels.
776 Smack maintains labels on file system objects using extended attributes. The
825 	all labels set on the filesystem. Not yet enforced.
828 	specifies a label to which all labels set on the