[lkml]   [1999]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 3dfx - a security hazard?

On Fri, 12 Mar 1999, David Luyer wrote:
> Because if you want anyone to be able to play games, you give them 3dfx
> access - ideally you'd want a group 3dfx[1]. If there's a way to crash the
> system with 3dfx, then you're not providing 3dfx properly, and you're just
> inviting people to introduce a security hazard.
> The same is definitely not true of /dev/mem - access to that is definitely
> restricted, and everybody knows that [or should].

Sorry, still not convinced. :)

Saying to a user who has just written his new flight simulator which
requires access to /dev/mem "oh no - access to this device is definitely
restricted!" is exactly the same as saying to another user whose new game
needs access to /dev/3dfx "oh no - this device is a security hole, can't
give you access to that!".

No difference, really.


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

 \ /
  Last update: 2005-03-22 13:50    [W:0.061 / U:9.808 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site