[lkml]   [1999]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject3dfx - a security hazard?
> It didnt - its a security hazard. Any user with access to it can crash
> the entire machine
> Alan

Dear Alan,

I am probably missing something, but access to both /dev/3dfx and (e.g.)
/dev/mem is controlled by filesystem permission rules. Writing garbage to
either will crash the entire machine. Why is one a security hazard and
another is not?

I think having 3dfx in the official kernel is a good idea - think about
it, if you have a 3dfx card you *will* install 3dfx module, be it
hazardous or otherwise. If you do not have 3dfx hardware it is silly
to compile the driver when configuring the kernel, thus all hazards
avoided automatically.

But, as I said, Alan is always right, so I am merely curious
as to what am I missing here.


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.043 / U:1.160 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site