SELinux - Date Index

• Thread Index

• Re: block_suspend everywhere...
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: block_suspend everywhere...
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: block_suspend everywhere...
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• Re: block_suspend everywhere...
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• block_suspend everywhere...
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• Lots of audits for "selinux_audit_rule_match: stale rule"
  • From: Andrew Ruch <adruch2002@xxxxxxxxx>
• Re: [PATCH] Security: List corruption occured during file system automation test
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• Re: [PATCH] Security: List corruption occured during file system automation test
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH] Security: List corruption occured during file system automation test
  • From: shivnandan.k@xxxxxxxxxxx
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH] libsemanage: Check files exist before sefcontext_compile
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [GIT PULL] SELinux/NetLabel fixes for 3.17 (attempt #2)
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [GIT PULL] SELinux/NetLabel fixes for 3.17
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• [GIT PULL] SELinux/NetLabel fixes for 3.17
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• [PATCH] selinux: remove unused variabled in the netport, netnode, and netif caches
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH] netlabel: fix the netlbl_catmap_setlong() dummy function
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Query regarding role hierarchy SELinux
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Debugging sepolgen-ifgen?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: confusing policy in unconfineddomain.te SEAndroid kk4.4
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• confusing policy in unconfineddomain.te SEAndroid kk4.4
  • From: Zhi Xin <xinzhi@xxxxxxxxxxx>
• Re: Debugging sepolgen-ifgen?
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• [PATCH v2] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH] selinux: Permit bounded transitions under NO_NEW_PRIVS or NOSUID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Debugging sepolgen-ifgen?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Debugging sepolgen-ifgen?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: [GIT PULL] SELinux patches for 3.17
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] Fix the NetLabel LSM category mappings
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [GIT PULL] SELinux patches for 3.17
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH 0/4] Fix the NetLabel LSM category mappings
  • From: David Miller <davem@xxxxxxxxxxxxx>
• tycho.nsa.gov mailing list memberships reminder
  • From: mailman-owner@xxxxxxxxxxxxx
• Re: [PATCH 4/4] netlabel: shorter names for the NetLabel catmap funcs/structs
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 3/4] netlabel: fix the catmap walking functions
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/4] netlabel: fix the horribly broken catmap functions
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/4] netlabel: fix a problem when setting bits below the previously lowest bit
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] Fix the NetLabel LSM category mappings
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• [PATCH 4/4] netlabel: shorter names for the NetLabel catmap funcs/structs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH 3/4] netlabel: fix the catmap walking functions
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH 2/4] netlabel: fix the horribly broken catmap functions
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH 1/4] netlabel: fix a problem when setting bits below the previously lowest bit
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH 0/4] Fix the NetLabel LSM category mappings
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH] crypto: properly label AF_ALG socket
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: %u in format string (no. 1) requires 'unsigned int *' but the argument type is 'int *'.
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• %u in format string (no. 1) requires 'unsigned int *' but the argument type is 'int *'.
  • From: Toralf Förster <toralf.foerster@xxxxxx>
• Re: [PATCH] crypto: properly label AF_ALG socket
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• [PATCH] crypto: properly label AF_ALG socket
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• How to access the Access Vector Cache from a LKM?
  • From: Thomas Coudray <amanone@xxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• [PATCH] Revert "selinux: fix the default socket labeling in sock_graft()"
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: do user space object managers really provide mandatory access control
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: do user space object managers really provide mandatory access control
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: do user space object managers really provide mandatory access control
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• RE: do user space object managers really provide mandatory access control
  • From: "Andy Warner" <warner@xxxxxxxxx>
• Re: do user space object managers really provide mandatory access control
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• Re: do user space object managers really provide mandatory access control
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• RE: do user space object managers really provide mandatory access control
  • From: "Andy Warner" <warner@xxxxxxxxx>
• do user space object managers really provide mandatory access control
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [mcstransd] Fails after Reload Translations
  • From: wenzong fan <wenzong.fan@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: What's a policy capability?
  • From: dE <de.techno@xxxxxxxxx>
• Re: What's a policy capability?
  • From: dE <de.techno@xxxxxxxxx>
• RE: File-system is not mounting when I am enabling selinux
  • From: Avijit Das <avijitnsec@xxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: What's a policy capability?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: How to build a simplified refpolicy?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: File-system is not mounting when I am enabling selinux
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: What's a policy capability?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: How to build a simplified refpolicy?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: File-system is not mounting when I am enabling selinux
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• How to build a simplified refpolicy?
  • From: kuangjiou <kuangjiou@xxxxxxxxxx>
• Re: What's a policy capability?
  • From: dE <de.techno@xxxxxxxxx>
• Re: File-system is not mounting when I am enabling selinux
  • From: dE <de.techno@xxxxxxxxx>
• File-system is not mounting when I am enabling selinux
  • From: Avijit Das <avijitnsec@xxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: What's a policy capability?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• What's a policy capability?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [GIT PULL] SELinux patches for 3.17
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: Initial SIDs.
  • From: dE <de.techno@xxxxxxxxx>
• [GIT PULL] SELinux patches for 3.17
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: why does kernel call setenforce
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: why does kernel call setenforce
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: why does kernel call setenforce
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: why does kernel call setenforce
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: why does kernel call setenforce
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• why does kernel call setenforce
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [mcstransd] Fails after Reload Translations
  • From: Joe Nall <joe@xxxxxxxx>
• [mcstransd] Fails after Reload Translations
  • From: wenzong fan <wenzong.fan@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [GIT PULL] SELinux fix for 3.16-rcX
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Initial SIDs.
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Initial SIDs.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Where does semanage store changes?
  • From: dE <de.techno@xxxxxxxxx>
• [GIT PULL] SELinux fix for 3.16-rcX
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH v2] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: NetLabel lead to kernel panic with some SELinux levels
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH v2] selinux: fix the default socket labeling in sock_graft()
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• NetLabel lead to kernel panic with some SELinux levels
  • From: Christian Evans <frodox@xxxxxxxx>
• Re: Fwd: [lca-announce] LCA CFP extended until Sunday 20th July 2014
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Dave Quigley <selinux@xxxxxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Dave Quigley <selinux@xxxxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Showing port Labels
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• [PATCH v2] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Showing port Labels
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Where does semanage store changes?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Audit support on ARM
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Fwd: [lca-announce] LCA CFP extended until Sunday 20th July 2014
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Showing port Labels
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Audit support on ARM
  • From: Dave Quigley <selinux@xxxxxxxxxxxxxxx>
• Showing port Labels
  • From: Dave Quigley <selinux@xxxxxxxxxxxxxxx>
• Where does semanage store changes?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: What's a 'permission map'?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: What's a 'permission map'?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: What's a 'permission map'?
  • From: dE <de.techno@xxxxxxxxx>
• Re: directory fcontext
  • From: dE <de.techno@xxxxxxxxx>
• [PATCH] selinux: fix the default socket labeling in sock_graft()
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: Suppress avc denial logs
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Suppress avc denial logs
  • From: Avijit Das <avijitnsec@xxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: pcre compiled context files invalid with pcre updates?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: pcre compiled context files invalid with pcre updates?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• libselinux 2.3 incompatibility
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: pcre compiled context files invalid with pcre updates?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: pcre compiled context files invalid with pcre updates?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• pcre compiled context files invalid with pcre updates?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: SELinux with overlayfs between squashfs and jffs2
  • From: David Quigley <selinux@xxxxxxxxxxxxxxx>
• Re: SELinux with overlayfs between squashfs and jffs2
  • From: Dave Quigley <dpquigl@xxxxxxxxxxxxxxx>
• SELinux with overlayfs between squashfs and jffs2
  • From: Antoine MOISE <antoine.moise@xxxxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• ANN: SETools 4 open-sourced
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• genhomedircon support for groups
  • From: Cretu Adrian <adycrt@xxxxxxxxx>
• Re: What's a 'permission map'?
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: What's a 'permission map'?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• What's a 'permission map'?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC PATCH] selinux: reduce the number of calls to synchronize_net() when flushing caches
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Listing restrictions on roles.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• [PATCH] LSM: Generalize existing module stacking
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] selinux: reduce the number of calls to synchronize_net() when flushing caches
  • From: Jaejyn Shin <flagon22bass@xxxxxxxxx>
• Re: secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Listing restrictions on roles.
  • From: dE <de.techno@xxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• secilc: is anyone able to confirm that type_change ...
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Laurent Bigonville <bigon@xxxxxxxxxx>
• Re: Enforcing default_user, default_role, default_type, default_range
  • From: dE <de.techno@xxxxxxxxx>
• Re: Enforcing default_user, default_role, default_type, default_range
  • From: dE <de.techno@xxxxxxxxx>
• Re: Enforcing default_user, default_role, default_type, default_range
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: Enforcing default_user, default_role, default_type, default_range
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: Enforcing default_user, default_role, default_type, default_range
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Listing restrictions on roles.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Enforcing default_user, default_role, default_type, default_range
  • From: dE <de.techno@xxxxxxxxx>
• Re: semanage commit forces CPU to 100%
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• Re: semanage commit forces CPU to 100%
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• semanage commit forces CPU to 100%
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• Listing restrictions on roles.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Weird un-audited denial on tmp_t
  • From: dE <de.techno@xxxxxxxxx>
• semanage commit forces CPU to 100%
  • From: Andy Ruch <adruch2002@xxxxxxxxx>
• libselinux-2.0.94-2.el6.i686 issue
  • From: Sebastian Brestin <sebastianbrestin@xxxxxxxxx>
• Re: Where's the class defined in file_contexts*
  • From: dE <de.techno@xxxxxxxxx>
• Re: Where's the class defined in file_contexts*
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Where's the class defined in file_contexts*
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Where's the class defined in file_contexts*
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Where's the class defined in file_contexts*
  • From: dE <de.techno@xxxxxxxxx>
• [RFC PATCH] selinux: reduce the number of calls to synchronize_net() when flushing caches
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• ANN: SELinux Userspace moved to GitHub
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH] Add db_exception and db_datatype support to label_db backend
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Jaejyn Shin <flagon22bass@xxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: Fwd: Booting time is increased after applying kernel 3.10
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Fwd: Booting time is increased after applying kernel 3.10
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• [PATCH] Add db_exception and db_datatype support to label_db backend
  • From: Artyom Smirnov <artyom.smirnov@xxxxxxxxxxxx>
• strange AVC message
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: [PATCH 0/2] Bug fixes for libsemanage/src/pywrap-test.py
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Different authentication with different user roles
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Different authentication with different user roles
  • From: Krzysztof Katowicz-Kowalewski <vnd@xxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] selinux: simple cleanup for cond_read_node()
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] selinux: simple cleanup for cond_read_node()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] selinux: simple cleanup for cond_read_node()
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• Re: [PATCH] selinux: introduce str_read() helper
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] selinux: fix a possible memory leak in cond_read_node()
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] selinux: simple cleanup for cond_read_node()
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: Deprecating policy capabilities
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] SELinux: use ARRAY_SIZE
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• [PATCH] SELinux: use ARRAY_SIZE
  • From: Himangi Saraogi <himangi774@xxxxxxxxx>
• [PATCH] selinux-testsuite: Add tests for exec transitions under NO_NEW_PRIVS
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH] selinux: introduce str_read() helper
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH 2/2] selinux: fix a possible memory leak in cond_read_node()
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH 1/2] selinux: simple cleanup for cond_read_node()
  • From: Namhyung Kim <namhyung@xxxxxxxxxx>
• [PATCH 2/2] libsemanage: use semanage_bool_get_value to print a boolean
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• [PATCH 1/2] libsemanage: fix src/pywrap-test.py -v -F
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• [PATCH 0/2] Bug fixes for libsemanage/src/pywrap-test.py
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• Re: [refpolicy] ANN: Reference Policy moved to GitHub
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: [refpolicy] ANN: Reference Policy moved to GitHub
  • From: Elia Pinto <andronicus.spiros@xxxxxxxxx>
• Re: ANN: Reference Policy moved to GitHub
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• [PATCH v2] selinux: Permit exec transitions under NO_NEW_PRIVS or NOSUID under certain circumstances.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] selinux: Permit transitions under NO_NEW_PRIVS or NOSUID under certain, circumstances.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH] selinux: Permit transitions under NO_NEW_PRIVS or NOSUID under certain, circumstances.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: SETools patch for libselinux-2.3
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: SETools patch for libselinux-2.3
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: SETools patch for libselinux-2.3
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• Re: Default context with context mount option.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Default context with context mount option.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Default context with context mount option.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• RE: Default context with context mount option.
  • From: David Caplan <dac@xxxxxxxxxx>
• Re: Default context with context mount option.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: SETools patch for libselinux-2.3
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: Deprecating policy capabilities
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• ANN: SETools moved to GitHub
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• ANN: Reference Policy moved to GitHub
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: Default context with context mount option.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: RBAC along with MLS?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Default context with context mount option.
  • From: Christian Evans <Frodox@xxxxxxxx>
• Default context with context mount option.
  • From: dE <de.techno@xxxxxxxxx>
• RBAC along with MLS?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Masahiro Yamada <yamada.m@xxxxxxxxxxxxxxxx>
• Re: [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Masahiro Yamada <yamada.m@xxxxxxxxxxxxxxxx>
• Re: How does matchpathcon/setfiles work?
  • From: dE <de.techno@xxxxxxxxx>
• Re: How does matchpathcon/setfiles work?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: How does matchpathcon/setfiles work?
  • From: dE <de.techno@xxxxxxxxx>
• Re: How does matchpathcon/setfiles work?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• How does matchpathcon/setfiles work?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [refpolicy] user_t more restrictive than sshd_t (e.g.)?
  • From: dE <de.techno@xxxxxxxxx>
• SETools patch for libselinux-2.3
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: attempting to run a sftpserver in a confined domain
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• attempting to run a sftpserver in a confined domain
  • From: "Kim Lawson-Jenkins" <kim.lawson-jenkins@xxxxxxxxxxxx>
• Re: change selinux user's roles
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: change selinux user's roles
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: change selinux user's roles
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: change selinux user's roles
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• change selinux user's roles
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: AVCs errors generated when CLI comands executed
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: user_t more restrictive than sshd_t (e.g.)?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: The use of fscontext(iso9660_t)
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• AVCs errors generated when CLI comands executed
  • From: "Kim Lawson-Jenkins" <kim.lawson-jenkins@xxxxxxxxxxxx>
• Re: user_t more restrictive than sshd_t (e.g.)?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [GIT PULL] SELinux patches for 3.16
  • From: James Morris <jmorris@xxxxxxxxx>
• The use of fscontext(iso9660_t)
  • From: dE <de.techno@xxxxxxxxx>
• secilc: issues with policy compiled by secilc
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: dE <de.techno@xxxxxxxxx>
• Re: SAMBA WITH SELINUX
  • From: dE <de.techno@xxxxxxxxx>
• Re: SAMBA WITH SELINUX
  • From: dE <de.techno@xxxxxxxxx>
• SAMBA WITH SELINUX
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• [PATCH] libselinux: fix typo in man page
  • From: Nicolas Iooss <nicolas.iooss@xxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: dE <de.techno@xxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• user_t more restrictive than sshd_t (e.g.)?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: dE <de.techno@xxxxxxxxx>
• Re: secilc CIL Reference Guide patches
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• secilc CIL Reference Guide patches
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [GIT PULL] SELinux patches for 3.16
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: dE <de.techno@xxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: secilc: in statement ordering limitations
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• secilc: in statement ordering limitations
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: [PATCH] selinux：cleanup redundant code in selinux_init()
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: Significance of SELinux user and roles on objects.
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Significance of SELinux user and roles on objects.
  • From: dE <de.techno@xxxxxxxxx>
• Re: How does SELinux work without roles?
  • From: dE <de.techno@xxxxxxxxx>
• Re: How does SELinux work without roles?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• system_u process does not have system_r
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH (for 3.15) 5/5] LSM: Remove duplicated rename handling.
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH (for 3.15) 3/5] AppArmor: Handle the rename flags.
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH (for 3.15) 1/5] LSM: Pass the rename flags to each LSM module.
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• How does SELinux work without roles?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: dE <de.techno@xxxxxxxxx>
• semanage: TypeError: cannot concatenate 'str' and 'NoneType' objects
  • From: Laurent Bigonville <bigon@xxxxxxxxxx>
• Re: create new roles for user
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: create new roles for user
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• create new roles for user
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• Re: secilc: classmappings do not work
  • From: James Carter <jwcart2@xxxxxxxxxxxxx>
• secilc: classmappings do not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Single init script for multiple daemons
  • From: Mladen Sekara <dev@xxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Single init script for multiple daemons
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Single init script for multiple daemons
  • From: Mladen Sekara <dev@xxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Single init script for multiple daemons
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Single init script for multiple daemons
  • From: Mladen Sekara <dev@xxxxxxxxxx>
• [RFC PATCH] selinux: prevent setting a security label on MNT_NOSUID applications
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH] selinux_init_load_policy: setenforce(0) if security_disable() fails
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Patches from Fedora on the sandbox package.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Presidency of user/role/type permissions.
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Presidency of user/role/type permissions.
  • From: dE <de.techno@xxxxxxxxx>
• [PATCH (for 3.15) 5/5] LSM: Remove duplicated rename handling.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH (for 3.15) 4/5] TOMOYO: Handle the rename flags.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH (for 3.15) 1/5] LSM: Pass the rename flags to each LSM module.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH (for 3.15) 3/5] AppArmor: Handle the rename flags.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH (for 3.15) 0/5] Fix cross rename regressions for LSM.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH (for 3.15) 2/5] SELinux: Handle the rename flags.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH (for 3.15) 0/5] Fix cross rename race window for LSM.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• [PATCH 4/4] seunshare: Try to use setcurrent before setexec
  • From: Dan Walsh <dwalsh@xxxxxxxxxx>
• [PATCH 3/4] Remove handling of cgroups from sandbox
  • From: Dan Walsh <dwalsh@xxxxxxxxxx>
• [PATCH 2/4] Update XDG_RUNTIME_DIR directory
  • From: Dan Walsh <dwalsh@xxxxxxxxxx>
• Patches from Fedora on the sandbox package.
  • From: Dan Walsh <dwalsh@xxxxxxxxxx>
• Re: [ANN] SELinux userspace release
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [ANN] SELinux userspace release
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Re: Refactor installation of policies and modules
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Refactor installation of policies and modules
  • From: Victor Porton <porton@xxxxxxxx>
• Re: svirt & labeled network
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: sshd and default security context.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• svirt & labeled network
  • From: vlad halilov <vlad.halilov@xxxxxxxxx>
• Re: sshd and default security context.
  • From: dE <de.techno@xxxxxxxxx>
• Re: selinux and static label for sVirt
  • From: vlad halilov <vlad.halilov@xxxxxxxxx>
• Re: selinux and static label for sVirt
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• selinux and static label for sVirt
  • From: vlad halilov <vlad.halilov@xxxxxxxxx>
• Re: [PATCH 1/1] add module for the entropy key daemon
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: sshd and default security context.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH 1/1] add module for the entropy key daemon
  • From: Petre Rodan <petre.rodan@xxxxxxxxxx>
• [PATCH 1/1] add ekeyd related rules
  • From: Petre Rodan <petre.rodan@xxxxxxxxxx>
• sshd and default security context.
  • From: dE <de.techno@xxxxxxxxx>
• Re: staff_u permission
  • From: Steve Huston <huston@xxxxxxxxxxxxxxxxxxx>
• Re: PAM modules ordering
  • From: Laurent Bigonville <bigon@xxxxxxxxxx>
• Re: PAM modules ordering
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• [ANN] SELinux userspace release
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• PAM modules ordering
  • From: Laurent Bigonville <bigon@xxxxxxxxxx>
• RE: No AVCs written to /var/log/messages
  • From: "Kim Lawson-Jenkins" <kim.lawson-jenkins@xxxxxxxxxxxx>
• Re: No AVCs written to /var/log/messages
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: No AVCs written to /var/log/messages
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• No AVCs written to /var/log/messages
  • From: "Kim Lawson-Jenkins" <kim.lawson-jenkins@xxxxxxxxxxxx>
• Re: How does policy loading work at bootup?
  • From: dE <de.techno@xxxxxxxxx>
• Re: How does policy loading work at bootup?
  • From: dE <de.techno@xxxxxxxxx>
• Re: What's a module exactly?
  • From: dE <de.techno@xxxxxxxxx>
• Re: staff_u permission
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• staff_u permission
  • From: Steve Huston <huston@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH (for 3.15) 0/5] Fix cross rename race window for LSM.
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: How does policy loading work at bootup?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: What's a module exactly?
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• What's a module exactly?
  • From: dE <de.techno@xxxxxxxxx>
• How does policy loading work at bootup?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: What's a policy configuration file?
  • From: dE <de.techno@xxxxxxxxx>
• Re: What's a policy configuration file?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: What's a policy configuration file?
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: What's a policy configuration file?
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: What's a policy configuration file?
  • From: dE <de.techno@xxxxxxxxx>
• Re: AVC cache size unit?
  • From: dE <de.techno@xxxxxxxxx>
• Re: What's a policy configuration file?
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: AVC cache size unit?
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• What's a policy configuration file?
  • From: dE <de.techno@xxxxxxxxx>
• Re: AVC cache size unit?
  • From: dE <de.techno@xxxxxxxxx>
• Re: AVC cache size unit?
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [RFC] Source Policy, CIL, and High Level Languages
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• tycho.nsa.gov mailing list memberships reminder
  • From: mailman-owner@xxxxxxxxxxxxx
• AVC cache size unit?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: William Roberts <bill.c.roberts@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: William Roberts <bill.c.roberts@xxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [PATCH] selinux_init_load_policy: setenforce(0) if security_disable() fails
  • From: Will Woods <wwoods@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: [PATCH] selinux_init_load_policy: setenforce(0) if security_disable() fails
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [RFC][PATCH] selinux: Report result in avc messages
  • From: William Roberts <bill.c.roberts@xxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• [RFC][PATCH] selinux: Report result in avc messages
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• Re: selinux_check_access() and unknown classes/perms
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• selinux_check_access() and unknown classes/perms
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• SELINUX=disabled vs. "enforce=1"
  • From: Will Woods <wwoods@xxxxxxxxxx>
• [PATCH] selinux_init_load_policy: setenforce(0) if security_disable() fails
  • From: Will Woods <wwoods@xxxxxxxxxx>
• [RFC] Source Policy, CIL, and High Level Languages
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH] setools: Update to load v29 policy source files.
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• Re: No chance of using SELinux on rootfs without security namespace?
  • From: dE <de.techno@xxxxxxxxx>
• Re: No chance of using SELinux on rootfs without security namespace?
  • From: Stephen Smalley <stephen.smalley@xxxxxxxxx>
• No chance of using SELinux on rootfs without security namespace?
  • From: dE <de.techno@xxxxxxxxx>
• fpp/cilpolicy potential bug
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Cannot enable selinux.
  • From: dE <de.techno@xxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH] setools: Update to load v29 policy source files.
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] setools: Update to load v29 policy source files.
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Steve Grubb <sgrubb@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH 6/6][v2] audit: send multicast messages only if there are listeners
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 5/6][v2] audit: add netlink multicast group for log read
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 4/6][v2] audit: add netlink audit protocol bind to check capabilities on multicast join
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 2/6][v2] netlink: have netlink per-protocol bind function return an error code.
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 3/6][v2] netlink: implement unbind to netlink_setsockopt NETLINK_DROP_MEMBERSHIP
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 1/6][v2] netlink: simplify nfnetlink_bind
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH 2/6] netlink: have netlink per-protocol bind function return an error code.
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 2/6] netlink: have netlink per-protocol bind function return an error code.
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [PATCH 0/6][v2] audit: implement multicast socket for journald
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: [secilc] typeattributeset with "and" expression does not work
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• [secilc] typeattributeset with "and" expression does not work
  • From: Dominick Grift <dominick.grift@xxxxxxxxx>
• Re: Cannot enable selinux.
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Cannot enable selinux.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Cannot enable selinux.
  • From: dE <de.techno@xxxxxxxxx>
• Re: In case you do not follow me on Twitter @rhatdan
  • From: dE <de.techno@xxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Allowing access other then permissive mode.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Allowing access other then permissive mode.
  • From: Kernel freak <kernelfreak@xxxxxxxxx>
• In case you do not follow me on Twitter @rhatdan
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Unreadable or missing xattr security.selinux on jffs2
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Unreadable or missing xattr security.selinux on jffs2
  • From: jkmeinde@xxxxxxxxxxxxxxxxxxx
• Re: Allowing access other then permissive mode.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: LIbselinux: Correctness of context decision, how its made?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Unreadable or missing xattr security.selinux on jffs2
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Unreadable or missing xattr security.selinux on jffs2
  • From: Judd Meinders <judd.meinders@xxxxxxxxxxxxxxxxxxx>
• Re: Why is SELINUXTYPE policy specific?
  • From: Sven Vermeulen <sven.vermeulen@xxxxxxxxx>
• Why is SELINUXTYPE policy specific?
  • From: dE <de.techno@xxxxxxxxx>
• Allowing access other then permissive mode.
  • From: Kernel freak <kernelfreak@xxxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Kernel freak <kernelfreak@xxxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Kernel freak <kernelfreak@xxxxxxxxx>
• Re: selinux_init_load_policy() and systemd switch-root
  • From: Will Woods <wwoods@xxxxxxxxxx>
• LIbselinux: Correctness of context decision, how its made?
  • From: Rastislav Hepner <rastislav.hepner@xxxxxxxxx>
• Unreadable or missing xattr security.selinux on jffs2
  • From: jkmeinde@xxxxxxxxxxxxxxxxxxx
• [PATCH 6/6] audit: send multicast messages only if there are listeners
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 5/6] audit: add netlink multicast group for log read
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 3/6] netlink: implement unbind to netlink_setsockopt NETLINK_DROP_MEMBERSHIP
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 4/6] audit: add netlink audit protocol bind to check capabilities on multicast join
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 2/6] netlink: have netlink per-protocol bind function return an error code.
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 0/6] audit: implement multicast socket for journald
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• [PATCH 1/6] netlink: simplify nfnetlink_bind
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: Transition domain in SELinux
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Transition domain in SELinux
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: selinux_init_load_policy() and systemd switch-root
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: selinux_init_load_policy() and systemd switch-root
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Transition domain in SELinux
  • From: toản cù <xuantoanbkfet@xxxxxxxxx>
• Re: [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• selinux_init_load_policy() and systemd switch-root
  • From: Will Woods <wwoods@xxxxxxxxxx>
• RE: Regarding call security_compute_av()
  • From: Bo Chen <bochen7e7@xxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Kernel freak <kernelfreak@xxxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Regarding call security_compute_av()
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Regarding call security_compute_av()
  • From: Kernel Geek <kernelfreak@xxxxxxxxx>
• [PATCH] selinux, kbuild: remove unnecessary $(hostprogs-y) from clean-files
  • From: Masahiro Yamada <yamada.m@xxxxxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Eric Paris <eparis@xxxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• [PATCH] libsepol: Skip duplicate filename_trans rules in state->out policy.
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• 2.3-rc1
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: [PATCH] setools: Update to load v29 policy source files.
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• [PATCH] setools: Update to load v29 policy source files.
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: /data used as two filesystem mountpoint，then seandroid how to lable file secontext?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: /data used as two filesystem mountpoint，then seandroid how to lable file secontext?
  • From: William Roberts <bill.c.roberts@xxxxxxxxx>
• /data used as two filesystem mountpoint，then seandroid how to lable file secontext?
  • From: ge <geshifei@xxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: Security server responses always based on class?
  • From: dE <de.techno@xxxxxxxxx>
• Re: Security server responses always based on class?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: Security server responses always based on class?
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Security server responses always based on class?
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx>
• Re: The purpose of SID.
  • From: dE <de.techno@xxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Steve Lawrence <slawrence@xxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: "Christopher J. PeBenito" <cpebenito@xxxxxxxxxx>
• [PATCH 4/4] setools: APOL Add default_objects and CIL policy namespaces tabs
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [PATCH 3/4] setools: APOL Add type, user, role bounds support
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [PATCH 1/4] setools: APOL Add constraints and filename transition support
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [PATCH 2/4] setools: APOL Add support for permissive types, polcaps, handle_unknown
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• [PATCH 0/4] APOL Enhancements to support additional policy features
  • From: Richard Haines <richard_c_haines@xxxxxxxxxxxxxx>
• Re: The purpose of SID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• Re: The purpose of SID.
  • From: Stephen Smalley <sds@xxxxxxxxxxxxx>
• The purpose of SID.
  • From: dE <de.techno@xxxxxxxxx>
• Re: What do you mean by a 'domain'.
  • From: "Patrick K., ITF" <cto@xxxxxxxxxxxxxxxxxx>
• Re: What do you mean by a 'domain'.
  • From: dE <de.techno@xxxxxxxxx>