messages from 2019-06-10 17:45:32 to 2019-07-01 19:22:58 UTC [more...]
[RFC PATCH v4 00/12] security: x86/sgx: SGX vs. LSM
2019-07-01 19:22 UTC (73+ messages)
` [RFC PATCH v4 01/12] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting
` [RFC PATCH v4 02/12] x86/sgx: Do not naturally align MAP_FIXED address
` [RFC PATCH v4 03/12] selftests: x86/sgx: Mark the enclave loader as not needing an exec stack
` [RFC PATCH v4 04/12] x86/sgx: Require userspace to define enclave pages' protection bits
` [RFC PATCH v4 05/12] x86/sgx: Enforce noexec filesystem restriction for enclaves
` [RFC PATCH v4 06/12] mm: Introduce vm_ops->may_mprotect()
` [RFC PATCH v4 07/12] LSM: x86/sgx: Introduce ->enclave_map() hook for Intel SGX
` [RFC PATCH v4 08/12] security/selinux: Require SGX_MAPWX to map enclave page WX
` [RFC PATCH v4 09/12] LSM: x86/sgx: Introduce ->enclave_load() hook for Intel SGX
` [RFC PATCH v4 10/12] security/selinux: Add enclave_load() implementation
` [RFC PATCH v4 11/12] security/apparmor: "
` [RFC PATCH v4 12/12] LSM: x86/sgx: Show line of sight to LSM support SGX2's EAUG
` [RFC PATCH v2 0/3] security/x86/sgx: SGX specific LSM hooks
` [RFC PATCH v2 1/3] x86/sgx: Add "
` [RFC PATCH v2 2/3] x86/sgx: Call LSM hooks from SGX subsystem/module
` [RFC PATCH v2 3/3] x86/sgx: Implement SGX specific hooks in SELinux
[PATCH v20 00/28] Intel SGX1 support
2019-06-27 20:32 UTC (4+ messages)
` [PATCH v20 22/28] x86/traps: Attempt to fixup exceptions in vDSO before signaling
LSM module for SGX?
2019-06-27 19:20 UTC (3+ messages)
[RFC PATCH v3 00/12] security: x86/sgx: SGX vs. LSM, round 3
2019-06-26 20:39 UTC (39+ messages)
` [RFC PATCH v3 01/12] x86/sgx: Add mm to enclave at mmap()
` [RFC PATCH v3 02/12] x86/sgx: Do not naturally align MAP_FIXED address
` [RFC PATCH v3 03/12] selftests: x86/sgx: Mark the enclave loader as not needing an exec stack
` [RFC PATCH v3 04/12] x86/sgx: Require userspace to define enclave pages' protection bits
` [RFC PATCH v3 05/12] x86/sgx: Enforce noexec filesystem restriction for enclaves
` [RFC PATCH v3 06/12] mm: Introduce vm_ops->may_mprotect()
` [RFC PATCH v3 07/12] LSM: x86/sgx: Introduce ->enclave_map() hook for Intel SGX
` [RFC PATCH v3 08/12] security/selinux: Require SGX_EXECMEM to map enclave page WX
` [RFC PATCH v3 09/12] LSM: x86/sgx: Introduce ->enclave_load() hook for Intel SGX
` [RFC PATCH v3 10/12] security/selinux: Add enclave_load() implementation
` [RFC PATCH v3 11/12] security/apparmor: "
` [RFC PATCH v3 12/12] LSM: x86/sgx: Show line of sight to LSM support SGX2's EAUG
[RFC PATCH] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting
2019-06-20 19:47 UTC (3+ messages)
[PATCH] x86/sgx: rip off the refcount from sgx_encl_add_page flow
2019-06-20 19:23 UTC (3+ messages)
[PATCH RFC] x86/sgx: Do not increase encl->refcount for VMAs
2019-06-20 19:08 UTC (7+ messages)
[PATCH RFC] x86/sgx: Check that the address is within ELRANGE
2019-06-19 12:24 UTC (3+ messages)
[RFC PATCH v1 0/3] security/x86/sgx: SGX specific LSM hooks
2019-06-18 15:40 UTC (33+ messages)
` [RFC PATCH v1 2/3] LSM/x86/sgx: Implement SGX specific hooks in SELinux
[RFC PATCH v2 0/5] security: x86/sgx: SGX vs. LSM
2019-06-17 16:38 UTC (25+ messages)
` [RFC PATCH v2 1/5] mm: Introduce vm_ops->may_mprotect()
` [RFC PATCH v2 2/5] x86/sgx: Require userspace to define enclave pages' protection bits
` [RFC PATCH v2 3/5] x86/sgx: Enforce noexec filesystem restriction for enclaves
` [RFC PATCH v2 5/5] security/selinux: Add enclave_load() implementation
[RFC PATCH 0/9] security: x86/sgx: SGX vs. LSM
2019-06-14 15:18 UTC (12+ messages)
` [RFC PATCH 2/9] x86/sgx: Do not naturally align MAP_FIXED address
[PATCH 0/7] x86/sgx: Clean up and enhance add pages ioctl
2019-06-13 19:45 UTC (25+ messages)
` [PATCH 4/7] x86/sgx: Allow userspace to add multiple pages in single ioctl()
` [PATCH 5/7] x86/sgx: Add flag to zero added region instead of copying from source
` [PATCH 7/7] x86/sgx: Add a reserved field to sgx_enclave_add_region to drop 'packed'
page: next (older) | prev (newer) | latest
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).