Lines Matching refs:labels

61 Smack uses extended attributes (xattrs) to store labels on filesystem
220 	    only allowed when subject's and object's labels are equal.
330 on what subjects can access which objects, based on the labels attached to
335 Smack labels are ASCII character strings. They can be up to 255 characters
337 Single character labels using special characters, that being anything
339 team. Smack labels are unstructured, case sensitive, and the only operation
340 ever performed on them is comparison for equality. Smack labels cannot
343 Smack labels cannot begin with a '-'. This is reserved for special options.
345 There are some predefined labels:
388 different labels is desired. One example is the familiar spy model of
392 mechanism for specifying rules allowing access between labels.
430 Spaces are not allowed in labels. Since a subject always has access to files
460 for two processes with different labels to share data without granting
472 tasks with identical Smack labels and requires no access checks.
483 immediately. For any pair of subject and object labels there can be only
522 label values to match the Smack labels being used without administrative
555 The mapping of Smack labels to CIPSO values is defined by writing to
631 to processes running with various labels.
635 Smack maintains labels on file system objects using extended attributes. The
679 	all labels set on the filesystem. Not yet enforced.
681 	smackfsfloor=label: specifies a label to which all labels set on the