Re: [PATCH] capabilities: implement per-process securebits

2008-02-22 Thread Serge E. Hallyn
Quoting Andrew G. Morgan ([EMAIL PROTECTED]): > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Andrew G. Morgan wrote: > | Serge E. Hallyn wrote: > | |> It all looks good to me. > | | > | |> Since we've confirmed that wireshark uses capabilities it must be > using > | |>

Re: [PATCH] capabilities: implement per-process securebits

2008-02-22 Thread Serge E. Hallyn
Quoting Andrew G. Morgan ([EMAIL PROTECTED]): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew G. Morgan wrote: | Serge E. Hallyn wrote: | | It all looks good to me. | | | | Since we've confirmed that wireshark uses capabilities it must be using | | prctl(PR_SET_KEEPCAPS), so

Re: [PATCH] capabilities: implement per-process securebits

2008-02-21 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew G. Morgan wrote: | Serge E. Hallyn wrote: | |> It all looks good to me. | | | |> Since we've confirmed that wireshark uses capabilities it must be using | |> prctl(PR_SET_KEEPCAPS), so running it might be a good way to verify that | |> your

Re: [PATCH] capabilities: implement per-process securebits

2008-02-21 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Serge E. Hallyn wrote: |> It all looks good to me. | |> Since we've confirmed that wireshark uses capabilities it must be using |> prctl(PR_SET_KEEPCAPS), so running it might be a good way to verify that |> your changes to that codepath (with

Re: [PATCH] capabilities: implement per-process securebits

2008-02-21 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Serge E. Hallyn wrote: | It all looks good to me. | | Since we've confirmed that wireshark uses capabilities it must be using | prctl(PR_SET_KEEPCAPS), so running it might be a good way to verify that | your changes to that codepath (with

Re: [PATCH] capabilities: implement per-process securebits

2008-02-21 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew G. Morgan wrote: | Serge E. Hallyn wrote: | | It all looks good to me. | | | | Since we've confirmed that wireshark uses capabilities it must be using | | prctl(PR_SET_KEEPCAPS), so running it might be a good way to verify that | | your

Re: [PATCH] capabilities: implement per-process securebits

2008-02-20 Thread Serge E. Hallyn
Quoting Andrew G. Morgan ([EMAIL PROTECTED]): > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Andrew > > Here is the patch to add per-process securebits again. This version > includes Serge's argument type fix (thanks), but is otherwise unchanged > from the one posted a couple of weeks back.

Re: [PATCH] capabilities: implement per-process securebits

2008-02-20 Thread Serge E. Hallyn
Quoting Andrew G. Morgan ([EMAIL PROTECTED]): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Here is the patch to add per-process securebits again. This version includes Serge's argument type fix (thanks), but is otherwise unchanged from the one posted a couple of weeks back. It is

[PATCH] capabilities: implement per-process securebits

2008-02-18 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Here is the patch to add per-process securebits again. This version includes Serge's argument type fix (thanks), but is otherwise unchanged from the one posted a couple of weeks back. It is against Linus' tree as of a the 15th. This change

[PATCH] capabilities: implement per-process securebits

2008-02-18 Thread Andrew G. Morgan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Here is the patch to add per-process securebits again. This version includes Serge's argument type fix (thanks), but is otherwise unchanged from the one posted a couple of weeks back. It is against Linus' tree as of a the 15th. This change