Displaying 2 results from an estimated 2 matches for "a_mod".
Did you mean:
s_mod
2003 May 16
3
open and euid security flaw in 5.0-Current?
On a FreeBSD 5.0 the behaviour of screen when connecting to other
users sessions have changed. Previously:
1. login as userA start a screen as userA and disconnect
2. login as root su - userA "screen -r"
3. result failure as userA cant access the ttyX with such a message
Current:
1. login as userA start a screen as userA and disconnect
2. login as root su - userA "screen -r"
3.
2008 Aug 31
0
NFSv4 ACLs.
...;struct acl". VOP_ACCESS changed a little - second
argument was changed from "int" to "vaccess_t"; there should be no
functional changes related to that. There are differences related to
permissions granularity; as long as VOP_ACCESS implementation simply
passes the "a_mode" parameter to the proper vaccess(9) routine, there
should be no difference in behaviour.
Adding granularity required adding some VWHATEVER defines to sys/vnode.h,
adding several VOP_ACCESS checks in the syscall layer, replacing VADMIN
with more specific permission in UFS and adding a unixify...