[lkml]   [2006]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC/PATCH] revoke/frevoke system calls V2
Ar Llu, 2006-08-07 am 22:52 +0000, ysgrifennodd David Wagner:
> I'm still trying to understand the semantics of this proposed
> frevoke() implementation. Can an attacker use this to forcibly
> close some other processes' file descriptor? Suppose the target


> process has fd 0 open and the attacker revokes the file corresponding
> to fd 0; what is the state of fd 0 in the target process? Is it
> closed? If the target process then open()s another file, does it

No its revoked. Just like a tty hangup

> get bound to fd 0? (Recall that open() always binds to the lowest
> unused fd.) If the answers are "yes", then the security consequences
> seem very scary.

Of course it doesn't. The BSD folk who added revoke were security people
not idiots.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-08-08 13:55    [W:0.090 / U:3.856 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site