On Fri, Jul 21, 2017 at 1:37 PM, Kees Cook wrote:
> On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote:
>> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
>>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook
On Fri, Jul 21, 2017 at 1:37 PM, Kees Cook wrote:
> On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote:
>> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
>>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
> Alternatively, if
On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote:
> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
>>> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore
On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote:
> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
>>> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
Alternatively, if you've got a fairly recent git repo with all the
On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
>> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
>>> Alternatively, if you've got a fairly recent git repo with all the
On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote:
> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
>> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
>>> Alternatively, if you've got a fairly recent git repo with all the
>>> patches merged I can build a test kernel and give it a shot for
On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
>> Alternatively, if you've got a fairly recent git repo with all the
>> patches merged I can build a test kernel and give it a shot for you,
>>
On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote:
> On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
>> Alternatively, if you've got a fairly recent git repo with all the
>> patches merged I can build a test kernel and give it a shot for you,
>> although fair warning it may take a day or two
On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
> Alternatively, if you've got a fairly recent git repo with all the
> patches merged I can build a test kernel and give it a shot for you,
> although fair warning it may take a day or two for me to get to it.
Hurm, I think
On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote:
> Alternatively, if you've got a fairly recent git repo with all the
> patches merged I can build a test kernel and give it a shot for you,
> although fair warning it may take a day or two for me to get to it.
Hurm, I think this will take quite
On Wed, Jul 19, 2017 at 9:37 PM, Kees Cook wrote:
> On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
>> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook
On Wed, Jul 19, 2017 at 9:37 PM, Kees Cook wrote:
> On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
>> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>>> The SELinux bprm_secureexec hook can be merged with the
On Wed, Jul 19, 2017 at 5:19 PM, Paul Moore wrote:
> On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
>> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>>> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
>>> hook since it's dealing with the same information, and all
On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
>> hook since it's dealing with the same information, and all of the
On Wed, Jul 19, 2017 at 8:03 PM, Paul Moore wrote:
> On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
>> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
>> hook since it's dealing with the same information, and all of the details
>> are finalized during the first call to
On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
> hook since it's dealing with the same information, and all of the details
> are finalized during the first call to the bprm_set_creds hook via
>
On Tue, Jul 18, 2017 at 6:25 PM, Kees Cook wrote:
> The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
> hook since it's dealing with the same information, and all of the details
> are finalized during the first call to the bprm_set_creds hook via
> prepare_binprm()
The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
hook since it's dealing with the same information, and all of the details
are finalized during the first call to the bprm_set_creds hook via
prepare_binprm() (subsequent calls due to binfmt_script, etc, are ignored
via
The SELinux bprm_secureexec hook can be merged with the bprm_set_creds
hook since it's dealing with the same information, and all of the details
are finalized during the first call to the bprm_set_creds hook via
prepare_binprm() (subsequent calls due to binfmt_script, etc, are ignored
via
20 matches
Mail list logo