linux-audit  

Messages by Thread

• • [PATCH v38 12/39] LSM: Use lsmblob in security_audit_rule_match Casey Schaufler
  • [PATCH v38 13/39] LSM: Use lsmblob in security_kernel_act_as Casey Schaufler
  • [PATCH v38 14/39] LSM: Use lsmblob in security_secctx_to_secid Casey Schaufler
  • [PATCH v38 15/39] LSM: Use lsmblob in security_secid_to_secctx Casey Schaufler
  • [PATCH v38 16/39] LSM: Use lsmblob in security_ipc_getsecid Casey Schaufler
  • [PATCH v38 17/39] LSM: Use lsmblob in security_current_getsecid Casey Schaufler
  • [PATCH v38 19/39] LSM: Use lsmblob in security_cred_getsecid Casey Schaufler
  • [PATCH v38 20/39] LSM: Specify which LSM to display Casey Schaufler
  • Re: [PATCH v38 20/39] LSM: Specify which LSM to display Mickaël Salaün
  • [PATCH v38 18/39] LSM: Use lsmblob in security_inode_getsecid Casey Schaufler
  • [PATCH v38 23/39] LSM: Use lsmcontext in security_inode_getsecctx Casey Schaufler
  • [PATCH v38 21/39] LSM: Ensure the correct LSM context releaser Casey Schaufler
  • [PATCH v38 22/39] LSM: Use lsmcontext in security_secid_to_secctx Casey Schaufler
  • [PATCH v38 24/39] Use lsmcontext in security_dentry_init_security Casey Schaufler
  • [PATCH v38 26/39] NET: Store LSM netlabel data in a lsmblob Casey Schaufler
  • [PATCH v38 25/39] LSM: security_secid_to_secctx in netlink netfilter Casey Schaufler
  • [PATCH v38 27/39] binder: Pass LSM identifier for confirmation Casey Schaufler
  • [PATCH v38 28/39] LSM: security_secid_to_secctx module selection Casey Schaufler
  • [PATCH v38 29/39] Audit: Keep multiple LSM data in audit_names Casey Schaufler
  • [PATCH v38 30/39] Audit: Create audit_stamp structure Casey Schaufler
  • [PATCH v38 32/39] Audit: Allow multiple records in an audit_buffer Casey Schaufler
  • [PATCH v38 33/39] Audit: Add record for multiple task security contexts Casey Schaufler
  • [PATCH v38 35/39] Audit: Add record for multiple object contexts Casey Schaufler
  • [PATCH v38 34/39] audit: multiple subject lsm values for netlabel Casey Schaufler
  • [PATCH v38 36/39] netlabel: Use a struct lsmblob in audit data Casey Schaufler
  • [PATCH v38 37/39] LSM: Removed scaffolding function lsmcontext_init Casey Schaufler
  • [PATCH v38 38/39] AppArmor: Remove the exclusive flag Casey Schaufler
  • [PATCH v38 31/39] LSM: Add a function to report multiple LSMs Casey Schaufler
  • [PATCH v38 39/39] LSM: Create lsm_module_list system call Casey Schaufler
  • Re: [PATCH v38 39/39] LSM: Create lsm_module_list system call kernel test robot
  • Re: [PATCH v38 39/39] LSM: Create lsm_module_list system call Kees Cook
  • Re: [PATCH v38 39/39] LSM: Create lsm_module_list system call Casey Schaufler
  • Re: [PATCH v38 39/39] LSM: Create lsm_module_list system call Mickaël Salaün
  • Re: [PATCH v38 39/39] LSM: Create lsm_module_list system call Casey Schaufler
• [PATCH RFC] LSM: Specify which LSM to display Casey Schaufler
• Query regarding the lib audit-userspace Manojkiran Eda
  • Re: Query regarding the lib audit-userspace Steve Grubb
  • Re: Query regarding the lib audit-userspace Manojkiran Eda
  • Re: Query regarding the lib audit-userspace Burn Alting
• [PATCH RFC] LSM: lsm_self_attr system call to get security module attributes Casey Schaufler
  • Re: [PATCH RFC] LSM: lsm_self_attr system call to get security module attributes Serge E. Hallyn
  • [PATCH v2 RFC] LSM: lsm_self_attr syscall for LSM self attributes Casey Schaufler
• Re: [PATCH -next] audit: remove selinux_audit_rule_update() declaration Paul Moore
• Re: [RFC PATCH 2/2] fs/xattr: wire up syscalls Christian Brauner
  • Re: [RFC PATCH 2/2] fs/xattr: wire up syscalls Richard Guy Briggs
• [PATCH] audit: remove obvious unnecessary header files wuchi
  • Re: [PATCH] audit: remove obvious unnecessary header files Paul Moore
  • Re: [PATCH] audit: remove obvious unnecessary header files chi wu
  • Re: [PATCH] audit: remove obvious unnecessary header files Paul Moore
  • Re: [PATCH] audit: remove obvious unnecessary header files chi wu
  • Re: [PATCH] audit: remove obvious unnecessary header files kernel test robot
  • Re: [PATCH] audit: remove obvious unnecessary header files kernel test robot
• audit-3.0.9 released Steve Grubb
• [PATCH] audit: use time_after to compare time wuchi
  • Re: [PATCH] audit: use time_after to compare time Paul Moore
• [GIT PULL] Audit fixes for v6.0 (#2) Paul Moore
  • Re: [GIT PULL] Audit fixes for v6.0 (#2) pr-tracker-bot
• [PATCH ghak138 v2 0/4] issues from moving beyond syscalls Richard Guy Briggs
  • [PATCH ghak138 v2 3/4] audit: free audit_proctitle only on task exit Richard Guy Briggs
  • Re: [PATCH ghak138 v2 3/4] audit: free audit_proctitle only on task exit Paul Moore
  • [PATCH ghak138 v2 4/4] audit: move audit_return_fixup before the filters Richard Guy Briggs
  • Re: [PATCH ghak138 v2 4/4] audit: move audit_return_fixup before the filters Paul Moore
  • [PATCH ghak138 v2 1/4] audit: audit_context pid unused, context enum comment fix Richard Guy Briggs
  • Re: [PATCH ghak138 v2 1/4] audit: audit_context pid unused, context enum comment fix Paul Moore
  • [PATCH ghak138 v2 2/4] audit: explicitly check audit_context->context enum value Richard Guy Briggs
  • Re: [PATCH ghak138 v2 2/4] audit: explicitly check audit_context->context enum value Paul Moore
• [PATCH ghak138] audit: move audit_return_fixup before the filters Richard Guy Briggs
  • Re: [PATCH ghak138] audit: move audit_return_fixup before the filters Paul Moore
  • Re: [PATCH ghak138] audit: move audit_return_fixup before the filters Richard Guy Briggs
• [PATCH] tests/io_uring: ensure that tne io_uring::enter_ring_fd is imported Paul Moore
  • Re: [PATCH] tests/io_uring: ensure that tne io_uring::enter_ring_fd is imported Richard Guy Briggs
  • Re: [PATCH] tests/io_uring: ensure that tne io_uring::enter_ring_fd is imported Paul Moore
  • Re: [PATCH] tests/io_uring: ensure that tne io_uring::enter_ring_fd is imported Richard Guy Briggs
• [GIT PULL] Audit fixes for v6.0 (#1) Paul Moore
  • Re: [GIT PULL] Audit fixes for v6.0 (#1) pr-tracker-bot
• [PATCH next] audit: printk before dropping logs in audit_log_end Ecronic
  • Re: [PATCH next] audit: printk before dropping logs in audit_log_end Paul Moore
  • Re: [PATCH next] audit: printk before dropping logs in audit_log_end Gaosheng Cui
  • Re: [PATCH next] audit: printk before dropping logs in audit_log_end Paul Moore
  • Re: [PATCH next] audit: printk before dropping logs in audit_log_end Gaosheng Cui
• Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Jan Kara
  • Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Paul Moore
  • Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Jan Kara
  • Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Paul Moore
  • Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Jan Kara
  • Re: [PATCH next] audit: fix potential double free on error path from fsnotify_add_inode_mark Paul Moore
• data-race in audit_log_start / audit_receive Abhishek Shah
  • Re: data-race in audit_log_start / audit_receive Paul Moore
  • Re: data-race in audit_log_start / audit_receive Paul Moore
  • Re: data-race in audit_log_start / audit_receive Gabriel Ryan
  • Re: data-race in audit_log_start / audit_receive Paul Moore
  • Re: data-race in audit_log_start / audit_receive Gabriel Ryan
• [PATCH] kernel: fix repeated words in comments Jilin Yuan
  • Re: [PATCH] kernel: fix repeated words in comments Paul Moore
• [PATCH v4 0/4] fanotify: Allow user space to pass back additional audit info Richard Guy Briggs
  • [PATCH v4 1/4] fanotify: Ensure consistent variable type for response Richard Guy Briggs
  • [PATCH v4 2/4] fanotify: define struct members to hold response decision context Richard Guy Briggs
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Amir Goldstein
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Jan Kara
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context kernel test robot
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Richard Guy Briggs
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Richard Guy Briggs
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Jan Kara
  • Re: [PATCH v4 2/4] fanotify: define struct members to hold response decision context Jan Kara
  • [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Richard Guy Briggs
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Steve Grubb
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Richard Guy Briggs
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Steve Grubb
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Paul Moore
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Steve Grubb
  • Re: [PATCH v4 4/4] fanotify, audit: deliver fan_info as a hex-encoded string Richard Guy Briggs
  • [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response kernel test robot
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Jan Kara
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Paul Moore
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Jan Kara
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 3/4] fanotify, audit: Allow audit to use the full permission event response Steve Grubb
  • Re: [PATCH v4 3/4] fanotify,audit: Allow audit to use the full permission event response Richard Guy Briggs
  • Re: [PATCH v4 0/4] fanotify: Allow user space to pass back additional audit info Amir Goldstein
• [PATCH] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Peilin Ye
  • Re: [PATCH] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Paul Moore
  • Re: [PATCH] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Paul Moore
  • Re: [PATCH] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Jens Axboe
  • Re: [PATCH] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Peilin Ye
  • [PATCH v2] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Peilin Ye
  • Re: [PATCH v2] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Paul Moore
  • Re: [PATCH v2] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Jens Axboe
  • Re: [PATCH v2] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Paul Moore
  • Re: [PATCH v2] audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker() Jens Axboe
• LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Steve Grubb
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Paul Moore
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Casey Schaufler
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? John Johansen
  • Re: LSM stacking in next for 6.1? Tetsuo Handa
  • Re: LSM stacking in next for 6.1? Kees Cook
  • Re: LSM stacking in next for 6.1? Casey Schaufler

• Earlier messages
• Later messages