<snip>
> >
> > Richard Gooch <Richard.Gooch@atnf.CSIRO.AU> wrote:
> > > There could be similar potential security problems with ordinary
> > > disc-based device nodes and kmod too, it would seem.
> >
> > Why? Device files have permissions on them.
>
> Hm. OK. That's something that I could do with devfsd. However, it
> still seems to me that loading a driver should never compromise your
> system. If it does the driver is broken.
>
In a perfect world that may be true, since however we live in an
imperfect
world, and we all make mistakes, security will probably continued to be
compromised by drivers/daemons/etc. When a problem is discovered they
are fixed. So yes in a perfect world a driver/daemon/etc should
compromise
a system, however in the imperfect world we live in they do.
<snip>
>
> Well, I cover the reasons in the FAQ. One other reason I should get
> around to adding: security. I expect many systems will not want to
> change device permissions (the drivers provide sensible defaults). In
> that case if some random hacker frobs the permissions on /dev/sda*
> then the next reboot gives you back the default (safe) permissions.
>
This to me seems like a really bad idea.
Once a system has been compromised it would seem that you would
want to keep as much "evidence" as possible. Resetting the
permissions at the next reboot would be destroy some "evidence".
This may also be the only piece of "evidence" that is readily visible.
<snip>
>
> Regards,
>
> Richard....
>
-- Terry L. Ridder Blue Danube Software (Blaue Donau Software) "We do not write software, we compose it."When the toast is burnt and all the milk has turned and Captain Crunch is waving farewell when the Big One finds you may this song remind you that they don't serve breakfast in hell ==Breakfast==Newsboys
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html