On Tue, 02 Jul 2002 13:58:50 PDT, Crispin Cowan said: > *Risk:* what if the kernel adds a new hook, and you (module writer) > don't notice? And it's important to your security model, i.e. Chris adds > the "kick Richard's module in the nads? Y/N" hook :) and Richard doesn't > notice. I'm assuming the risk model here is "new functionality allows an attacker to get around your model" (for instance, a hypothetical model that mediated open()/close() breaking when mmap() is added...) This raises a second concern - who's job is it to watch the kernel and make sure that new hooks are added in functionality when needed? This is important. Otherwise, ALL us module writers/users could be hung out to dry if a new feature is added that doesn't have the needed hooks... -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech
This archive was generated by hypermail 2b30 : Tue Jul 02 2002 - 14:19:32 PDT