| /linux-5.10/security/smack/ |
| D | smack_access.c | 56 * @subject_label: a pointer to the subject's Smack label
60 * This function looks up the subject/object pair in the
104 * smk_access - determine if a subject has a specific access to an object
105 * @subject: a pointer to the subject's Smack label entry
110 * This function looks up the subject/object pair in the
116 int smk_access(struct smack_known *subject, struct smack_known *object, in smk_access() argument
126 * A star subject can't access any object. in smk_access()
128 if (subject == &smack_known_star) { in smk_access()
133 * An internet object can be accessed by any subject. in smk_access()
135 * An internet subject can access any object. in smk_access()
[all …]
|
| /linux-5.10/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 134 This interface reports whether a subject with the specified
142 This interface reports whether a subject with the specified
159 where the first string is the subject label, the second the
162 "rwxat-". If a rule for a given subject and object exists it will be
223 where the first string is the subject label, the second the
238 where the first string is the subject label, the second the
293 For the ``PTRACE_READ`` a subject needs to have a read access on
298 only allowed when subject's and object's labels are equal.
305 revoke-subject
307 rules with that subject label.
[all …]
|
| /linux-5.10/crypto/asymmetric_keys/ |
| D | x509_parser.h | 18 char *subject; /* Name of certificate subject */ member
20 struct asymmetric_key_id *skid; /* Subject + subjectKeyId (optional) */
31 const void *raw_subject; /* Raw subject name in ASN.1 */
|
| D | x509_public_key.c | 173 pr_devel("Cert Subject: %s\n", cert->subject); in x509_key_preparse()
199 sulen = strlen(cert->subject); in x509_key_preparse()
212 p = memcpy(desc, cert->subject, sulen); in x509_key_preparse()
|
| /linux-5.10/drivers/net/ethernet/mscc/ |
| D | ocelot.h | 78 * ENTRYTYPE_NORMAL is subject to aging.
79 * ENTRYTYPE_LOCKED is not subject to aging.
80 * ENTRYTYPE_MACv4 is not subject to aging. For IPv4 multicast.
81 * ENTRYTYPE_MACv6 is not subject to aging. For IPv6 multicast.
|
| /linux-5.10/Documentation/security/ |
| D | credentials.rst | 52 A subject is an object that is acting upon another object.
65 A subject has an additional interpretation of its credentials. A subset
68 subject acts.
77 Linux has a number of actions available that a subject may perform upon an
78 object. The set of actions available depends on the nature of the subject
86 When a subject acts upon an object, a security calculation is made. This
88 action, and searching one or more sets of rules to see whether the subject
101 is an abbreviated ACL with three fixed classes of subject ('user',
118 subject label, the object label and the action and look for a rule
|
| /linux-5.10/include/uapi/drm/ |
| D | vgem_drm.h | 10 * permit persons to whom the Software is furnished to do so, subject to
37 * subject to backwards-compatibility constraints.
|
| D | qxl_drm.h | 10 * Software is furnished to do so, subject to the following conditions:
34 * subject to backwards-compatibility constraints.
|
| D | virtgpu_drm.h | 10 * Software is furnished to do so, subject to the following conditions:
34 * subject to backwards-compatibility constraints.
|
| /linux-5.10/include/xen/ |
| D | xenbus_dev.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| D | acpi.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/arch/x86/include/asm/xen/ |
| D | hypervisor.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/arch/arm/xen/ |
| D | grant-table.c | 11 * software packages, subject to the following license:
17 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 114 following subject lines (``yyyy-mm-dd`` is the date of the pull
124 so please read up on it. The subject line must indicate whether the
128 For fixes eventually landing in bpf -> net tree, the subject must
131 git format-patch --subject-prefix='PATCH bpf' start..finish
134 bpf-next -> net-next, the subject must look like::
136 git format-patch --subject-prefix='PATCH bpf-next' start..finish
140 problem either if the subject line says net or net-next as target.
150 version number (``v2``, ``v3``, ...) into the subject prefix::
152 git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
233 be subject to change.
[all …]
|
| /linux-5.10/include/keys/ |
| D | asymmetric-type.h | 36 * (2) Issuer & Subject Unique IDs. Optional. These were the original way to
39 * (3) Auth & Subject Key Identifiers. Optional. SKIDs are only provided on
|
| /linux-5.10/Documentation/process/ |
| D | submitting-patches.rst | 350 Include PATCH in the subject
354 convention to prefix your subject line with [PATCH]. This lets Linus
527 understand the subject area and to perform thorough reviews, will normally
561 The canonical patch subject line is::
563 Subject: [PATCH 001/123] subsystem: summary phrase
584 The Subject line format makes it very easy to sort the emails
585 alphabetically by subject line - pretty much any email reader will
589 The ``subsystem`` in the email's Subject should identify which
592 The ``summary phrase`` in the email's Subject should concisely
615 brackets: "Subject: [PATCH <tag>...] <summary phrase>". The tags are
[all …]
|
| /linux-5.10/drivers/xen/ |
| D | acpi.c | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/drivers/crypto/cavium/zip/ |
| D | zip_deflate.h | 28 * This Software, including technical data, may be subject to U.S. export
30 * associated regulations, and may be subject to export or import
|
| D | zip_inflate.h | 28 * This Software, including technical data, may be subject to U.S. export
30 * associated regulations, and may be subject to export or import
|
| D | zip_mem.h | 28 * This Software, including technical data, may be subject to U.S. export
30 * associated regulations, and may be subject to export or import
|
| D | zip_crypto.h | 28 * This Software, including technical data, may be subject to U.S. export
30 * associated regulations, and may be subject to export or import
|
| /linux-5.10/include/uapi/xen/ |
| D | evtchn.h | 13 * software packages, subject to the following license:
19 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/include/xen/arm/ |
| D | hypercall.h | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|
| /linux-5.10/Documentation/devicetree/bindings/ |
| D | submitting-patches.rst | 14 be a separate patch. The preferred subject prefix for binding patches is::
18 The 80 characters of the subject are precious. It is recommended to not
|
| /linux-5.10/arch/arm64/xen/ |
| D | hypercall.S | 12 * software packages, subject to the following license:
18 * and to permit persons to whom the Software is furnished to do so, subject to
|