#
272461 |
|
02-Oct-2014 |
gjb |
Copy stable/10@r272459 to releng/10.1 as part of the 10.1-RELEASE process.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
261828 |
|
13-Feb-2014 |
brueffer |
MFC: r261566
Use CAP_EVENT instead of the deprecated CAP_POLL_EVENT.
PR: 185382 (based on) Submitted by: Loganaden Velvindron Reviewed by: pjd
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
248603 |
|
21-Mar-2013 |
pjd |
Update regression tests after adding chflagsat(2).
Sponsored by: The FreeBSD Foundation
|
#
248396 |
|
16-Mar-2013 |
pjd |
Update the tests now that absence of the O_APPEND flag requires CAP_SEEK capability. Add some more tests.
Sponsored by: The FreeBSD Foundation
|
#
248394 |
|
16-Mar-2013 |
pjd |
The mode argument for open(2)/openat(2) only makes sense if the O_CREAT flag was given.
Sponsored by: The FreeBSD Foundation
|
#
247605 |
|
01-Mar-2013 |
pjd |
Update existing regression tests after Capsicum overhaul.
|
#
224910 |
|
16-Aug-2011 |
jonathan |
poll(2) implementation for capabilities.
When calling poll(2) on a capability, unwrap first and then poll the underlying object.
Approved by: re (kib), mentor (rwatson) Sponsored by: Google Inc
|
#
224797 |
|
12-Aug-2011 |
jonathan |
Rename CAP_*_KEVENT to CAP_*_EVENT.
Change the names of a couple of capability rights to be less FreeBSD-specific.
Approved by: re (kib), mentor (rwatson) Sponsored by: Google Inc
|
#
224778 |
|
11-Aug-2011 |
rwatson |
Second-to-last commit implementing Capsicum capabilities in the FreeBSD kernel for FreeBSD 9.0:
Add a new capability mask argument to fget(9) and friends, allowing system call code to declare what capabilities are required when an integer file descriptor is converted into an in-kernel struct file *. With options CAPABILITIES compiled into the kernel, this enforces capability protection; without, this change is effectively a no-op.
Some cases require special handling, such as mmap(2), which must preserve information about the maximum rights at the time of mapping in the memory map so that they can later be enforced in mprotect(2) -- this is done by narrowing the rights in the existing max_protection field used for similar purposes with file permissions.
In namei(9), we assert that the code is not reached from within capability mode, as we're not yet ready to enforce namespace capabilities there. This will follow in a later commit.
Update two capability names: CAP_EVENT and CAP_KEVENT become CAP_POST_KEVENT and CAP_POLL_KEVENT to more accurately indicate what they represent.
Approved by: re (bz) Submitted by: jonathan Sponsored by: Google Inc
|
#
224660 |
|
05-Aug-2011 |
jonathan |
Expect fchflags(2) to fail with EOPNOTSUPP on NFS.
Even if we have CAP_FCHFLAGS, fchflags(2) fails on NFS. This is normal and expected, so don't fail the test because of it.
Note that, whether or not we are on NFS, fchflags(2) should always fail with ENOTCAPABLE if we are using a capability that does not have the CAP_FCHFLAGS right.
Approved by: re (kib), mentor (rwatson) Sponsored by: Google Inc
|
#
224653 |
|
04-Aug-2011 |
jonathan |
Flesh out the cap_test regression test.
Add more regression testing, some of which is expected to fail until we commit more kernel implementation.
Approved by: re (kib), mentor (rwatson) Sponsored by: Google Inc
|