| /linux-6.15/security/landlock/ |
| D | task.c | 270 const struct landlock_cred_security *const subject = in hook_unix_stream_connect() local
275 if (!subject) in hook_unix_stream_connect()
281 if (!sock_is_scoped(other, subject->domain)) in hook_unix_stream_connect()
284 landlock_log_denial(subject, &(struct landlock_request) { in hook_unix_stream_connect()
301 const struct landlock_cred_security *const subject = in hook_unix_may_send() local
305 if (!subject) in hook_unix_may_send()
318 if (!sock_is_scoped(other->sk, subject->domain)) in hook_unix_may_send()
321 landlock_log_denial(subject, &(struct landlock_request) { in hook_unix_may_send()
344 const struct landlock_cred_security *subject; in hook_task_kill() local
362 subject = landlock_get_applicable_subject(cred, signal_scope, in hook_task_kill()
[all …]
|
| D | fs.c | 957 const struct landlock_cred_security *const subject = in current_check_access_path() local
962 if (!subject) in current_check_access_path()
965 access_request = landlock_init_layer_masks(subject->domain, in current_check_access_path()
968 if (is_access_to_paths_allowed(subject->domain, path, access_request, in current_check_access_path()
973 landlock_log_denial(subject, &request); in current_check_access_path()
1134 const struct landlock_cred_security *const subject = in current_check_refer_path() local
1144 if (!subject) in current_check_refer_path()
1171 subject->domain, in current_check_refer_path()
1174 if (is_access_to_paths_allowed(subject->domain, new_dir, in current_check_refer_path()
1180 landlock_log_denial(subject, &request1); in current_check_refer_path()
[all …]
|
| D | audit.c | 387 * @subject: The Landlock subject's credential denying an action.
390 void landlock_log_denial(const struct landlock_cred_security *const subject, in landlock_log_denial() argument
398 if (WARN_ON_ONCE(!subject || !subject->domain || in landlock_log_denial()
399 !subject->domain->hierarchy || !request)) in landlock_log_denial()
410 subject->domain, &missing, request->layer_masks, in landlock_log_denial()
418 get_hierarchy(subject->domain, youngest_layer); in landlock_log_denial()
422 get_hierarchy(subject->domain, youngest_layer); in landlock_log_denial()
440 if (subject->domain_exec & BIT(youngest_layer)) { in landlock_log_denial()
|
| D | net.c | 58 const struct landlock_cred_security *const subject = in current_check_access_socket() local
62 if (!subject) in current_check_access_socket()
177 rule = landlock_find_rule(subject->domain, id); in current_check_access_socket()
178 access_request = landlock_init_layer_masks(subject->domain, in current_check_access_socket()
186 landlock_log_denial(subject, in current_check_access_socket()
|
| D | audit.h | 58 void landlock_log_denial(const struct landlock_cred_security *const subject,
69 landlock_log_denial(const struct landlock_cred_security *const subject, in landlock_log_denial() argument
|
| /linux-6.15/security/smack/ |
| D | smack_access.c | 58 * @subject_label: a pointer to the subject's Smack label
62 * This function looks up the subject/object pair in the
105 * smk_access - determine if a subject has a specific access to an object
106 * @subject: a pointer to the subject's Smack label entry
111 * This function looks up the subject/object pair in the
117 int smk_access(struct smack_known *subject, struct smack_known *object, in smk_access() argument
127 * A star subject can't access any object. in smk_access()
129 if (subject == &smack_known_star) { in smk_access()
134 * An internet object can be accessed by any subject. in smk_access()
136 * An internet subject can access any object. in smk_access()
[all …]
|
| /linux-6.15/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-6.15/crypto/asymmetric_keys/ |
| D | x509_parser.h | 19 char *subject; /* Name of certificate subject */ member
21 struct asymmetric_key_id *skid; /* Subject + subjectKeyId (optional) */
32 const void *raw_subject; /* Raw subject name in ASN.1 */
|
| D | x509_public_key.c | 162 pr_devel("Cert Subject: %s\n", cert->subject); in x509_key_preparse()
181 sulen = strlen(cert->subject); in x509_key_preparse()
193 p = memcpy(desc, cert->subject, sulen); in x509_key_preparse()
|
| /linux-6.15/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-6.15/Documentation/process/ |
| D | submitting-patches.rst | 375 weeks with the word "RESEND" added to the subject line::
385 Include PATCH in the subject
389 convention to prefix your subject line with [PATCH]. This lets Linus
588 understand the subject area and to perform thorough reviews, will normally
646 Subject Line
649 The canonical patch subject line is::
651 Subject: [PATCH 001/123] subsystem: summary phrase
672 The Subject line format makes it very easy to sort the emails
673 alphabetically by subject line - pretty much any email reader will
677 The ``subsystem`` in the email's Subject should identify which
[all …]
|
| /linux-6.15/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.
|
| /linux-6.15/include/xen/ |
| D | xenbus_dev.h | 10 * software packages, subject to the following license:
16 * 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-6.15/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-6.15/LICENSES/dual/ |
| D | CC-BY-4.0 | 33 original works of authorship and other material subject to copyright
47 material not subject to the license. This includes other CC-
85 a. Adapted Material means material subject to Copyright and Similar
121 g. Licensed Rights means the rights granted to You subject to the
151 1. Subject to the terms and conditions of this Public License,
226 Your exercise of the Licensed Rights is expressly made subject to the
|
| D | copyleft-next-0.3.1 | 22 Subject to the terms of this License, I grant You:
103 longer subject to the conditions in sections 3 through 5.
114 a license to My Work from Me, subject to the terms of this License.
130 rights of those who have received copies or rights from You subject to
|
| /linux-6.15/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 142 following subject lines (``yyyy-mm-dd`` is the date of the pull
153 so please read up on it. The subject line must indicate whether the
157 For fixes eventually landing in bpf -> net tree, the subject must
160 git format-patch --subject-prefix='PATCH bpf' start..finish
163 bpf-next -> net-next, the subject must look like::
165 git format-patch --subject-prefix='PATCH bpf-next' start..finish
169 problem either if the subject line says net or net-next as target.
179 version number (``v2``, ``v3``, ...) into the subject prefix::
181 git format-patch --subject-prefix='PATCH bpf-next v2' start..finish
264 be subject to change.
[all …]
|
| /linux-6.15/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_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
|
| 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
|
| /linux-6.15/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-6.15/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-6.15/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
|