Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct

On Thu, 2007-09-20 at 08:36 -0700, Casey Schaufler wrote:

> Ok, what can't be copied, and why can't it be copied?

In practice, no security information can be copied because the checks
are all made on the "current" pointer. There is no mechanism other than
'current' for passing security information around.

Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct
    • From: Casey Schaufler <[email protected]>

• Prev by Date: Re: sys_chroot+sys_fchdir Fix
• Next by Date: Re: [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental.
• Previous by thread: Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct
• Next by thread: Re: [PATCH 3/3] CRED: Move the effective capabilities into the cred struct
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]