> > this hides more kernel pointers in the kinfo proc struct and
> > introduces a backdoor for the kmem group. also hoist the permission
> > test up out of the loops.
>
> Why should we have a backdoor for the group kmem? There are several
> programs installed setgid kmem and this could expose tho
On Sat, Mar 23, 2013 at 14:19, Todd C. Miller wrote:
> On Sat, 23 Mar 2013 06:55:40 -0400, Ted Unangst wrote:
>
>> this hides more kernel pointers in the kinfo proc struct and
>> introduces a backdoor for the kmem group. also hoist the permission
>> test up out of the loops.
>
> Why should we hav
On Sat, 23 Mar 2013 06:55:40 -0400, Ted Unangst wrote:
> this hides more kernel pointers in the kinfo proc struct and
> introduces a backdoor for the kmem group. also hoist the permission
> test up out of the loops.
Why should we have a backdoor for the group kmem? There are several
programs ins
this hides more kernel pointers in the kinfo proc struct and
introduces a backdoor for the kmem group. also hoist the permission
test up out of the loops.
Index: sys/sysctl.h
===
RCS file: /cvs/src/sys/sys/sysctl.h,v
retrieving revisi
