| /Linux-v5.4/security/smack/ |
| D | smack_access.c | 116 int smk_access(struct smack_known *subject, struct smack_known *object, in smk_access() argument
128 if (subject == &smack_known_star) { in smk_access()
137 if (object == &smack_known_web || subject == &smack_known_web) in smk_access()
148 if (subject->smk_known == object->smk_known) in smk_access()
158 if (subject == &smack_known_hat) in smk_access()
169 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
170 &subject->smk_rules); in smk_access()
193 if (subject == smack_unconfined) in smk_access()
200 smack_log(subject->smk_known, object->smk_known, in smk_access()
320 audit_log_untrustedstring(ab, sad->subject); in smack_log_callback()
[all …]
|
| /Linux-v5.4/crypto/asymmetric_keys/ |
| D | x509_public_key.c | 170 pr_devel("Cert Subject: %s\n", cert->subject); in x509_key_preparse()
196 sulen = strlen(cert->subject); in x509_key_preparse()
209 p = memcpy(desc, cert->subject, sulen); in x509_key_preparse()
|
| D | x509_parser.h | 18 char *subject; /* Name of certificate subject */ member
|
| D | x509.asn1 | 13 subject Name ({ x509_note_subject }),
|
| D | pkcs7_verify.c | 215 x509->subject, in pkcs7_verify_sig_chain()
295 pr_debug("- subject %s\n", p->subject); in pkcs7_verify_sig_chain()
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/ |
| D | submitting-patches.txt | 10 be a separate patch. The preferred subject prefix for binding patches is:
14 The 80 characters of the subject are precious. It is recommended to not
|
| /Linux-v5.4/Documentation/networking/ |
| D | ax25.txt | 9 of the message, the subject field is ignored. You don't need to be
|
| /Linux-v5.4/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-v5.4/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 119 following subject lines (``yyyy-mm-dd`` is the date of the pull
129 so please read up on it. The subject line must indicate whether the
133 For fixes eventually landing in bpf -> net tree, the subject must
136 git format-patch --subject-prefix='PATCH bpf' start..finish
139 bpf-next -> net-next, the subject must look like::
141 git format-patch --subject-prefix='PATCH bpf-next' start..finish
145 problem either if the subject line says net or net-next as target.
155 version number (``v2``, ``v3``, ...) into the subject prefix::
157 git format-patch --subject-prefix='PATCH net-next v2' start..finish
238 be subject to change.
[all …]
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | arm-realview-eb-11mp-bbrevd.dts | 9 * furnished to do so, subject to the following conditions:
|
| D | arm-realview-eb-a9mp-bbrevd.dts | 9 * furnished to do so, subject to the following conditions:
|
| D | arm-realview-eb-bbrevd.dts | 9 * furnished to do so, subject to the following conditions:
|
| D | arm-realview-eb-11mp-bbrevd-ctrevb.dts | 9 * furnished to do so, subject to the following conditions:
|
| /Linux-v5.4/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/ |
| D | gpcgk104.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | gpcgk110.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | gpcgk208.fuc5 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | gpcgm107.fuc5 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgf100.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgf117.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgk104.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgk110.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgk208.fuc5 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | hubgm107.fuc5 | 9 * Software is furnished to do so, subject to the following conditions:
|
| D | gpcgf100.fuc3 | 9 * Software is furnished to do so, subject to the following conditions:
|
