Lines Matching full:security

2  * Linux Security Module interfaces
28 #include <linux/security.h>
33 * union security_list_options - Linux Security Module hook function list
35 * Security hooks for program execution operations.
38 * If the setup in prepare_exec_creds did not setup @bprm->cred->security
40 * @bprm->cred->security to be what commit_creds needs to install for the
42 * (e.g. for transitions between security domains).
55 * between security domains).
64 * begin. It allows a check against the @bprm->cred->security value
71 * Prepare to install the new security attributes of a process being
80 * Tidy up after the installation of the new security attributes of a
87 * Security hooks for mount using fs_context.
91 * Allocate and attach a security structure to sc->security. This pointer
103 * Security hooks for filesystem operations.
106 * Allocate and attach a security structure to the sb->s_security field.
138 * so that the security module can extract security-specific mount
140 * This also allows the original mount data to be stripped of security-
143 * @copy copied data which will be passed to the security module.
146 * Extracts security system specific mount options and verifies no changes
167 * Set the security relevant mount options used for a superblock
168 * @sb the superblock to set security mount options for
171 * Copy all security options from a given superblock to another
177 * Parse a string of security data filling in the opts structure
204 * Security hooks for inode operations.
207 * Allocate and attach a security structure to @inode->i_security. The
214 * Deallocate the inode security structure and set @inode->i_security to
217 * Obtain the security attribute name suffix and value to set on a newly
218 * created inode and set up the incore security field for the new inode.
224 * If the security module does not use security attributes or does
225 * not wish to put a security attribute on this particular inode,
234 * -EOPNOTSUPP if no security attribute is needed, or
237 * Set up the incore security field for the new anonymous inode
238 * and return whether the inode creation is permitted by the security
243 * Returns 0 on success, -EACCES if the security module denies the
384 * existing Linux permission function, so a security module can use it to
413 * Update inode security field after successful setxattr operation.
429 * security label associated with @name for @inode via @buffer. Note that
430 * @name is the remainder of the attribute name after the security prefix
435 * Set the security label associated with @name for @inode from the
439 * security. prefix has been removed.
442 * Copy the extended attribute names for the security labels
454 * The setuid bit is being removed. Remove similar security labels.
466 * overlay filesystem. Security module can prepare a set of new creds
478 * security module does not know about attribute or a negative error code
482 * Fill in @inode security information for a @dentry if allowed.
488 * Security hooks for kernfs node operations
491 * Initialize the security context of a newly created kernfs node based
497 * Security hooks for file operations
501 * called by various operations that read or write files. A security
511 * Security modules must handle this separately if they need such
517 * Allocate and attach a security structure to the file->f_security field.
518 * The security field is initialized to NULL when the structure is first
523 * Deallocate and free any security structures stored in file->f_security.
532 * should never be used by the security module.
564 * never be used by the security module.
570 * Save owner security information (typically from current->security) in
578 * struct file, so the file structure (and associated security information)
585 * This hook allows security modules to control the ability of a process
594 * Security hooks for task operations.
612 * Deallocate and clear the cred->security field in a set of credentials.
623 * Retrieve the security identifier of the cred structure @c
629 * @secid specifies the security ID to be set
710 * Retrieve the security identifier of the process @p.
782 * Set the security attributes for an inode based on an associated task's
783 * security attributes, e.g. for /proc/pid inodes.
787 * Security hooks for Netlink messaging.
790 * Save security information for a netlink message so that permission
791 * checking can be performed when the message is processed. The security
800 * Security hooks for Unix domain networking.
826 * Security hooks for socket operations.
836 * This hook allows a module to update or allocate a per-socket security
837 * structure. Note that the security field was not added directly to the
838 * socket structure, but rather, the socket security information is stored
840 * allocate and attach security information to
933 * This hook allows the security module to provide peer socket security
938 * @optval userspace memory where the security state is to be copied.
940 * of the security state.
946 * This hook allows the security module to provide peer socket security
950 * security state returned by this hook for a packet via the SCM_SECURITY
957 * Allocate and attach a security structure to the sk->sk_security field,
958 * which is used to copy security attributes between local stream sockets.
960 * Deallocate security structure.
962 * Clone/copy security structure.
985 * This hook allows a module to allocate a security structure for a TUN
987 * @security pointer to a security structure pointer.
990 * This hook allows a module to free the security structure for a TUN
992 * @security pointer to the TUN device's security structure
997 * @security pointer to the TUN device's security structure.
999 * This hook can be used by the module to update any security state
1002 * @security pointer to the TUN device's security structure.
1004 * This hook can be used by the module to update any security state
1005 * associated with the TUN device's security structure.
1006 * @security pointer to the TUN devices's security structure.
1008 * Security hooks for SCTP
1012 * the security module.
1035 * Security hooks for Infiniband
1041 * @sec pointer to a security structure.
1046 * @sec pointer to a security structure.
1048 * Allocate a security structure for Infiniband objects.
1049 * @sec pointer to a security structure pointer.
1052 * Deallocate an Infiniband security structure.
1053 * @sec contains the security structure to be freed.
1055 * Security hooks for XFRM operations.
1058 * @ctxp is a pointer to the xfrm_sec_ctx being added to Security Policy
1060 * @sec_ctx contains the security context information being provided by
1062 * Allocate a security structure to the xp->security field; the security
1069 * Allocate a security structure in new_ctxp that contains the
1074 * Deallocate xp->security.
1077 * Authorize deletion of xp->security.
1079 * @x contains the xfrm_state being added to the Security Association
1081 * @sec_ctx contains the security context information being provided by
1083 * Allocate a security structure to the x->security field; the security
1088 * @x contains the xfrm_state being added to the Security Association
1090 * @polsec contains the policy's security context.
1093 * Allocate a security structure to the x->security field; the security
1099 * Deallocate x->security.
1102 * Authorize deletion of x->security.
1106 * @fl_secid contains the flow security label that is used to authorize
1125 * Security hooks affecting all Key Management operations
1128 * Permit allocation of a key and assign security data. Note that key does
1134 * Notification of destruction; free security data.
1142 * evaluate the security data on the key.
1146 * Get a textual representation of the security context attached to a key
1157 * Security hooks affecting all System V IPC operations.
1170 * Security hooks for individual messages held in System V IPC message queues
1173 * Allocate and attach a security structure to the msg->security field.
1174 * The security field is initialized to NULL when the structure is first
1179 * Deallocate the security structure for this message.
1182 * Security hooks for System V IPC Message Queues
1185 * Allocate and attach a security structure to the
1186 * @perm->security field. The security field is initialized to
1191 * Deallocate security field @perm->security for the message queue.
1227 * Security hooks for System V Shared Memory Segments
1230 * Allocate and attach a security structure to the @perm->security
1231 * field. The security field is initialized to NULL when the structure is
1236 * Deallocate the security structure @perm->security for the memory segment.
1262 * Security hooks for System V Semaphores
1265 * Allocate and attach a security structure to the @perm->security
1266 * field. The security field is initialized to NULL when the structure is
1271 * Deallocate security structure @perm->security for the semaphore.
1320 * Security modules may also want to perform a process tracing check
1323 * binprm_security_ops if the process is being traced and its security
1359 * @opts contains options for the capable check <include/linux/security.h>
1392 * Convert secid to security context. If secdata is NULL the length of
1397 * @secid contains the security ID.
1398 * @secdata contains the pointer that stores the converted security
1402 * Convert security context to secid.
1403 * @secid contains the pointer to the generated security ID.
1404 * @secdata contains the security context.
1407 * Release the security context.
1408 * @secdata contains the security context.
1409 * @seclen contains the length of the security context.
1411 * Security hooks for Audit
1432 * @secid contains the security id in question.
1444 * Notify the security module that it must revalidate the security context
1448 * Notify the security module of what the security context of an inode
1449 * should be. Initializes the incore security context managed by the
1450 * security module for this inode. Example usage: NFS client invokes
1451 * this hook to initialize the security context in its incore inode to the
1455 * @inode we wish to set the security context of.
1460 * Change the security context of an inode. Updates the
1461 * incore security context managed by the security module and invokes the
1464 * this hook to change the security context in its incore inode and on the
1468 * @dentry contains the inode we wish to set the security context of.
1473 * On success, returns 0 and fills out @ctx and @ctxlen with the security
1475 * @inode we wish to get the security context of.
1476 * @ctx is a pointer in which to place the allocated security context.
1479 * Security hooks for the general notification queue:
1493 * Security hooks for using the eBPF maps and programs functionalities through
1498 * into the kernel. The actual security module can implement their own
1515 * Initialize the security field inside bpf map.
1518 * Clean up the security information stored inside bpf map.
1521 * Initialize the security field inside bpf program.
1524 * Clean up the security information stored inside bpf prog.
1532 * Security hooks for perf events
1537 * Allocate and save perf_event security info.
1539 * Release (free) perf_event security info.
1541 * Read perf_event security info if allowed.
1543 * Write perf_event security info if allowed.
1558 * Security module hook list structure.
1569 * Security blob size or offset data.
1633 * Assuring the safety of deleting a security module is up to
1634 * the security module involved. This may entail ordering the