Re: [PULL] seccomp update (next)

2016-07-07 Thread James Morris
On Thu, 7 Jul 2016, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. Pulled, thanks. -- James Morris

Re: [PULL] seccomp update (next)

2016-07-07 Thread James Morris
On Thu, 7 Jul 2016, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. Pulled, thanks. -- James Morris

Re: [PULL] seccomp update (next)

2016-06-19 Thread Andy Lutomirski
On Sat, Jun 18, 2016 at 3:21 AM, Andy Lutomirski wrote: > On Jun 18, 2016 12:02 AM, "Kees Cook" wrote: >> >> On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski >> wrote: >> > On Fri, Jun 17, 2016 at 12:15 AM, James Morris

Re: [PULL] seccomp update (next)

2016-06-19 Thread Andy Lutomirski
On Sat, Jun 18, 2016 at 3:21 AM, Andy Lutomirski wrote: > On Jun 18, 2016 12:02 AM, "Kees Cook" wrote: >> >> On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski >> wrote: >> > On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: >> >> On Tue, 14 Jun 2016, Kees Cook wrote: >> >> >> >>> Hi, >>

Re: [PULL] seccomp update (next)

2016-06-18 Thread Andy Lutomirski
On Jun 18, 2016 12:02 AM, "Kees Cook" wrote: > > On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski wrote: > > On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: > >> On Tue, 14 Jun 2016, Kees Cook wrote: > >> > >>> Hi, > >>> >

Re: [PULL] seccomp update (next)

2016-06-18 Thread Andy Lutomirski
On Jun 18, 2016 12:02 AM, "Kees Cook" wrote: > > On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski wrote: > > On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: > >> On Tue, 14 Jun 2016, Kees Cook wrote: > >> > >>> Hi, > >>> > >>> Please pull these seccomp changes for next. These have been

Re: [PULL] seccomp update (next)

2016-06-18 Thread Kees Cook
On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski wrote: > On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: >> On Tue, 14 Jun 2016, Kees Cook wrote: >> >>> Hi, >>> >>> Please pull these seccomp changes for next. These have been tested by >>> myself

Re: [PULL] seccomp update (next)

2016-06-18 Thread Kees Cook
On Fri, Jun 17, 2016 at 11:55 AM, Andy Lutomirski wrote: > On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: >> On Tue, 14 Jun 2016, Kees Cook wrote: >> >>> Hi, >>> >>> Please pull these seccomp changes for next. These have been tested by >>> myself and Andy, and close a long-standing issue

Re: [PULL] seccomp update (next)

2016-06-17 Thread Andy Lutomirski
On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: > On Tue, 14 Jun 2016, Kees Cook wrote: > >> Hi, >> >> Please pull these seccomp changes for next. These have been tested by >> myself and Andy, and close a long-standing issue with seccomp where tracers >> could change the

Re: [PULL] seccomp update (next)

2016-06-17 Thread Andy Lutomirski
On Fri, Jun 17, 2016 at 12:15 AM, James Morris wrote: > On Tue, 14 Jun 2016, Kees Cook wrote: > >> Hi, >> >> Please pull these seccomp changes for next. These have been tested by >> myself and Andy, and close a long-standing issue with seccomp where tracers >> could change the syscall out from

Re: [PULL] seccomp update (next)

2016-06-17 Thread James Morris
On Tue, 14 Jun 2016, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. These have been tested by > myself and Andy, and close a long-standing issue with seccomp where tracers > could change the syscall out from under seccomp. Pulled to security -next. -- James Morris

Re: [PULL] seccomp update (next)

2016-06-17 Thread James Morris
On Tue, 14 Jun 2016, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. These have been tested by > myself and Andy, and close a long-standing issue with seccomp where tracers > could change the syscall out from under seccomp. Pulled to security -next. -- James Morris

Re: [PULL] seccomp update (next)

2015-07-20 Thread James Morris
On Wed, 15 Jul 2015, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. > > Thanks! > > -Kees > > The following changes since commit b3bddffd35a0b77eee89760eb94cafa18dc431f5: > > Merge branch 'next' of >

Re: [PULL] seccomp update (next)

2015-07-20 Thread James Morris
On Wed, 15 Jul 2015, Kees Cook wrote: Hi, Please pull these seccomp changes for next. Thanks! -Kees The following changes since commit b3bddffd35a0b77eee89760eb94cafa18dc431f5: Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next

Re: [PULL] seccomp update (next)

2014-12-01 Thread James Morris
On Mon, 1 Dec 2014, Kees Cook wrote: > On Mon, Dec 1, 2014 at 2:56 PM, James Morris wrote: > > On Mon, 1 Dec 2014, Kees Cook wrote: > > > >> On Thu, Nov 27, 2014 at 3:37 PM, James Morris wrote: > >> > On Wed, 26 Nov 2014, Kees Cook wrote: > >> > > >> >> > That would be because your tree is

Re: [PULL] seccomp update (next)

2014-12-01 Thread Kees Cook
On Mon, Dec 1, 2014 at 2:56 PM, James Morris wrote: > On Mon, 1 Dec 2014, Kees Cook wrote: > >> On Thu, Nov 27, 2014 at 3:37 PM, James Morris wrote: >> > On Wed, 26 Nov 2014, Kees Cook wrote: >> > >> >> > That would be because your tree is based on v3.17 and Kees' is based on >> >> > v3.18-rc6

Re: [PULL] seccomp update (next)

2014-12-01 Thread James Morris
On Mon, 1 Dec 2014, Kees Cook wrote: > On Thu, Nov 27, 2014 at 3:37 PM, James Morris wrote: > > On Wed, 26 Nov 2014, Kees Cook wrote: > > > >> > That would be because your tree is based on v3.17 and Kees' is based on > >> > v3.18-rc6 ... > >> > >> James, I can base on whatever you like. I can do

Re: [PULL] seccomp update (next)

2014-12-01 Thread Kees Cook
On Thu, Nov 27, 2014 at 3:37 PM, James Morris wrote: > On Wed, 26 Nov 2014, Kees Cook wrote: > >> > That would be because your tree is based on v3.17 and Kees' is based on >> > v3.18-rc6 ... >> >> James, I can base on whatever you like. I can do v3.17, or even >> against your security-next. It

Re: [PULL] seccomp update (next)

2014-12-01 Thread James Morris
On Mon, 1 Dec 2014, Kees Cook wrote: On Thu, Nov 27, 2014 at 3:37 PM, James Morris jmor...@namei.org wrote: On Wed, 26 Nov 2014, Kees Cook wrote: That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ... James, I can base on whatever you like. I can do

Re: [PULL] seccomp update (next)

2014-12-01 Thread Kees Cook
On Mon, Dec 1, 2014 at 2:56 PM, James Morris jmor...@namei.org wrote: On Mon, 1 Dec 2014, Kees Cook wrote: On Thu, Nov 27, 2014 at 3:37 PM, James Morris jmor...@namei.org wrote: On Wed, 26 Nov 2014, Kees Cook wrote: That would be because your tree is based on v3.17 and Kees' is based on

Re: [PULL] seccomp update (next)

2014-12-01 Thread James Morris
On Mon, 1 Dec 2014, Kees Cook wrote: On Mon, Dec 1, 2014 at 2:56 PM, James Morris jmor...@namei.org wrote: On Mon, 1 Dec 2014, Kees Cook wrote: On Thu, Nov 27, 2014 at 3:37 PM, James Morris jmor...@namei.org wrote: On Wed, 26 Nov 2014, Kees Cook wrote: That would be because your

Re: [PULL] seccomp update (next)

2014-12-01 Thread Kees Cook
On Thu, Nov 27, 2014 at 3:37 PM, James Morris jmor...@namei.org wrote: On Wed, 26 Nov 2014, Kees Cook wrote: That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ... James, I can base on whatever you like. I can do v3.17, or even against your security-next. It

Re: [PULL] seccomp update (next)

2014-11-27 Thread James Morris
On Wed, 26 Nov 2014, Kees Cook wrote: > > That would be because your tree is based on v3.17 and Kees' is based on > > v3.18-rc6 ... > > James, I can base on whatever you like. I can do v3.17, or even > against your security-next. It seems everyone uses something > different. :) It's best to

Re: [PULL] seccomp update (next)

2014-11-27 Thread James Morris
On Wed, 26 Nov 2014, Kees Cook wrote: That would be because your tree is based on v3.17 and Kees' is based on v3.18-rc6 ... James, I can base on whatever you like. I can do v3.17, or even against your security-next. It seems everyone uses something different. :) It's best to track my

Re: [PULL] seccomp update (next)

2014-11-26 Thread Kees Cook
On Wed, Nov 26, 2014 at 1:46 PM, Stephen Rothwell wrote: > Hi James, > > On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris > wrote: >> >> On Tue, 25 Nov 2014, Kees Cook wrote: >> >> > Please pull these seccomp changes for next. >> > >> > Thanks! >> > >> > -Kees >> > >> > The following

Re: [PULL] seccomp update (next)

2014-11-26 Thread Stephen Rothwell
Hi James, On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris wrote: > > On Tue, 25 Nov 2014, Kees Cook wrote: > > > Please pull these seccomp changes for next. > > > > Thanks! > > > > -Kees > > > > The following changes since commit 5d01410fe4d92081f349b013a2e7a95429e4f2c9: > > > >

Re: [PULL] seccomp update (next)

2014-11-26 Thread James Morris
On Tue, 25 Nov 2014, Kees Cook wrote: > Hi, > > Please pull these seccomp changes for next. > > Thanks! > > -Kees > > The following changes since commit 5d01410fe4d92081f349b013a2e7a95429e4f2c9: > > Linux 3.18-rc6 (2014-11-23 15:25:20 -0800) > > are available in the git repository at: >

Re: [PULL] seccomp update (next)

2014-11-26 Thread James Morris
On Tue, 25 Nov 2014, Kees Cook wrote: Hi, Please pull these seccomp changes for next. Thanks! -Kees The following changes since commit 5d01410fe4d92081f349b013a2e7a95429e4f2c9: Linux 3.18-rc6 (2014-11-23 15:25:20 -0800) are available in the git repository at:

Re: [PULL] seccomp update (next)

2014-11-26 Thread Stephen Rothwell
Hi James, On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris jmor...@namei.org wrote: On Tue, 25 Nov 2014, Kees Cook wrote: Please pull these seccomp changes for next. Thanks! -Kees The following changes since commit 5d01410fe4d92081f349b013a2e7a95429e4f2c9: Linux

Re: [PULL] seccomp update (next)

2014-11-26 Thread Kees Cook
On Wed, Nov 26, 2014 at 1:46 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi James, On Thu, 27 Nov 2014 00:23:06 +1100 (AEDT) James Morris jmor...@namei.org wrote: On Tue, 25 Nov 2014, Kees Cook wrote: Please pull these seccomp changes for next. Thanks! -Kees The