Hi Andy,
On 24 June 2017 at 10:13, Greg Kroah-Hartman wrote:
> On Thu, Jun 22, 2017 at 07:40:49PM -0700, Andy Lutomirski wrote:
>> Greg, for context, the issue here is that we made what was arguably a
>> design error in seccomp's interaction with ptrace. After determining
>> that fixing it solve
On Sat, Jun 24, 2017 at 06:45:37AM +0200, Greg Kroah-Hartman wrote:
> On Sat, Jun 24, 2017 at 02:34:07AM +0200, Luis R. Rodriguez wrote:
> > So taking the position that any kselftest script on linux-next or a future
> > kernel should never break stable implicate that *any* fix going upstream for
>
On Sat, Jun 24, 2017 at 02:34:07AM +0200, Luis R. Rodriguez wrote:
> So taking the position that any kselftest script on linux-next or a future
> kernel should never break stable implicate that *any* fix going upstream for
> which there is a respective ksefltest test *must* have a stable upstream f
On Thu, Jun 22, 2017 at 07:40:49PM -0700, Andy Lutomirski wrote:
> Greg, for context, the issue here is that we made what was arguably a
> design error in seccomp's interaction with ptrace. After determining
> that fixing it solved a bunch of problems and didn't break any user
> programs, we fixed
On Thu, Jun 22, 2017 at 07:40:49PM -0700, Andy Lutomirski wrote:
> On Thu, Jun 22, 2017 at 6:52 PM, Greg Kroah-Hartman
> wrote:
> > On Thu, Jun 22, 2017 at 10:50:43AM -0700, Kees Cook wrote:
> >> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
> >> > On Thu, Jun 22, 2017 at 10:09 AM, Shu
Hi Shuah,
On Fri, Jun 23, 2017 at 2:03 PM, Shuah Khan wrote:
> On 06/22/2017 01:48 PM, Tom Gall wrote:
>> Hi
>>
>> On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
>>> On 06/22/2017 11:50 AM, Kees Cook wrote:
On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
> On Thu, Jun 22,
On 06/22/2017 01:48 PM, Tom Gall wrote:
> Hi
>
> On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
>> On 06/22/2017 11:50 AM, Kees Cook wrote:
>>> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
> On 06/22/2017 10:53 AM, Kee
On 06/22/2017 10:02 PM, Sumit Semwal wrote:
> Hi Shuah,
>
> On 23 June 2017 at 01:53, Shuah Khan wrote:
>> Hi Tom,
>>
>> On 06/22/2017 01:48 PM, Tom Gall wrote:
>>> Hi
>>>
>>> On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
On 06/22/2017 11:50 AM, Kees Cook wrote:
> On Thu, Jun 22, 2
On Thu, Jun 22, 2017 at 7:40 PM, Andy Lutomirski wrote:
> On Thu, Jun 22, 2017 at 6:52 PM, Greg Kroah-Hartman
> wrote:
>> On Thu, Jun 22, 2017 at 10:50:43AM -0700, Kees Cook wrote:
>>> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
>>> > On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wr
Hi Shuah,
On 23 June 2017 at 01:53, Shuah Khan wrote:
> Hi Tom,
>
> On 06/22/2017 01:48 PM, Tom Gall wrote:
>> Hi
>>
>> On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
>>> On 06/22/2017 11:50 AM, Kees Cook wrote:
On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
> On Thu, Jun
On Thu, Jun 22, 2017 at 6:52 PM, Greg Kroah-Hartman
wrote:
> On Thu, Jun 22, 2017 at 10:50:43AM -0700, Kees Cook wrote:
>> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
>> > On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
>> >> On 06/22/2017 10:53 AM, Kees Cook wrote:
>> >>> On Th
On Thu, Jun 22, 2017 at 10:50:43AM -0700, Kees Cook wrote:
> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
> > On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
> >> On 06/22/2017 10:53 AM, Kees Cook wrote:
> >>> On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal
> >>> wrote:
> Hi
Hi Tom,
On 06/22/2017 01:48 PM, Tom Gall wrote:
> Hi
>
> On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
>> On 06/22/2017 11:50 AM, Kees Cook wrote:
>>> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
> On 06/22/2017 10:5
Hi
On Thu, Jun 22, 2017 at 2:06 PM, Shuah Khan wrote:
> On 06/22/2017 11:50 AM, Kees Cook wrote:
>> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
>>> On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
On 06/22/2017 10:53 AM, Kees Cook wrote:
> On Thu, Jun 22, 2017 at 9:18 A
On 06/22/2017 11:50 AM, Kees Cook wrote:
> On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
>> On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
>>> On 06/22/2017 10:53 AM, Kees Cook wrote:
On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal
wrote:
> Hi Kees, Andy,
>
>
On Thu, Jun 22, 2017 at 10:49 AM, Andy Lutomirski wrote:
> On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
>> On 06/22/2017 10:53 AM, Kees Cook wrote:
>>> On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal
>>> wrote:
Hi Kees, Andy,
On 15 June 2017 at 23:26, Sumit Semwal wrote:
>>
On Thu, Jun 22, 2017 at 10:09 AM, Shuah Khan wrote:
> On 06/22/2017 10:53 AM, Kees Cook wrote:
>> On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal
>> wrote:
>>> Hi Kees, Andy,
>>>
>>> On 15 June 2017 at 23:26, Sumit Semwal wrote:
3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] -
On 06/22/2017 10:53 AM, Kees Cook wrote:
> On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal wrote:
>> Hi Kees, Andy,
>>
>> On 15 June 2017 at 23:26, Sumit Semwal wrote:
>>> 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] -
>>> feature and test together.
>>> - This one also seems like a
On Thu, Jun 22, 2017 at 9:18 AM, Sumit Semwal wrote:
> Hi Kees, Andy,
>
> On 15 June 2017 at 23:26, Sumit Semwal wrote:
>> 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] -
>> feature and test together.
>> - This one also seems like a security hole being closed, and the
>> 'feature'
Hi Kees, Andy,
On 15 June 2017 at 23:26, Sumit Semwal wrote:
> 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] -
> feature and test together.
> - This one also seems like a security hole being closed, and the
> 'feature' could be a candidate for stable backports, but Arnd tried
> th
20 matches
Mail list logo
