Consider this my plea for module support build in to pl15, so getting
ftape to run with it will be much easier that it has been with pl13,
ALPHA pl13, and pl14.
Anyone else have feeling on this? (Linus??)
James
I agree! Or, how about the ftape stuff built in rather than as a loadable
module? If is it the only driver ever to use modules, there's not much
point in having them in the kernel, is there?
---
-------------------------------------------------------------------------------
Richard Evans Telephone : (+44) 223 566200
Tadpole Technology plc Fax : (+44) 223 566201
Cambridge Science Park
Milton Road E-Mail : r...@tadtec.co.uk
Cambridge, CB4 4WQ, UK
-------------------------------------------------------------------------------
>Consider this my plea for module support build in to pl15, so getting
>ftape to run with it will be much easier that it has been with pl13,
>ALPHA pl13, and pl14.
>Anyone else have feeling on this? (Linus??)
One rather obvious problem is that modules.tar represents a
security hole the size of Hudson bay. This is OK for tinkering
(especially when you're not on the net...), but for production
use it just won't do. Anyone have any idea how difficult it
would be to make a secure modules package?
--
O_ ---- Peter Dalgaard
c/ /' --- Statistical Research Unit
( ) \( ) -- University of Copenhagen
~~~~~~~~~~ - (p...@kubism.ku.dk)
... Anyone have any idea how difficult it
would be to make a secure modules package?
Only allow root to make the system call that loads code.
Brian
This and a check to see that the kernel release and module driver release
are the same was implemented some time ago by Bas (but not yet publically
released).
Hopefully with a bit of further cleaning up modules will apear in a future
offical kernel release.
With this I'm not aware of any security or reliability problems not already
present.
- Jon.