Page MenuHomeFreeBSD

Enable lookup_cap_dotdot and lookup_cap_dotdot_nonlocal by default.
ClosedPublic

Authored by kib on Dec 10 2016, 10:10 AM.
Referenced Files
Unknown Object (File)
Mar 15 2024, 1:55 PM
Unknown Object (File)
Mar 15 2024, 1:51 PM
Unknown Object (File)
Jan 9 2024, 5:14 AM
Unknown Object (File)
Jan 9 2024, 5:14 AM
Unknown Object (File)
Jan 9 2024, 5:13 AM
Unknown Object (File)
Jan 9 2024, 4:23 AM
Unknown Object (File)
Dec 27 2023, 7:48 PM
Unknown Object (File)
Dec 27 2023, 7:47 PM
Subscribers

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kib retitled this revision from to Enable lookup_cap_dotdot and lookup_cap_dotdot_nonlocal by default..
kib updated this object.
kib edited the test plan for this revision. (Show Details)
kib added reviewers: cem, emaste.
kib set the repository for this revision to rS FreeBSD src repository - subversion.
kib added a project: capsicum.
sys/kern/vfs_lookup.c
168 ↗(On Diff #22796)

Should nonlocal lookup be allowed by default?

For local dotdot lookups in capsicum mode, I think it will be very easy to add some unit tests confirming correct behavior.

In D8746#181220, @cem wrote:

For local dotdot lookups in capsicum mode, I think it will be very easy to add some unit tests confirming correct behavior.

Here's an initial stab at that: https://reviews.freebsd.org/D8748

sys/kern/vfs_lookup.c
168 ↗(On Diff #22796)

I do not see why not, now, at least in head. I am not sure about the original considerations about covert interactions between two clients, and suspect that the client-side incoherence is needed to even try to achieve the escape. I propose to keep this simple at least in head, and turn the knob off if working scenario is actually proposed.

cem edited edge metadata.
This revision is now accepted and ready to land.Dec 11 2016, 6:38 PM
This revision was automatically updated to reflect the committed changes.