[lkml]   [1996]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Misc Fixes
On Fri, 12 Jul 1996, Matthias Urlichs wrote:

> In, article <>,
> (Robey Pointer) writes:
> >
> > How about a small kernel function to return the current securelevel value?
> > int get_securelevel();
> > Then export THAT to modules.
> >
> The problem is that any truly malicious module can get the address of that
> function, look for the addresss of the securelevel variable, dereference
> that, and set it to zero.
> Duh.

(I'm generally ignorant about securelevel but ..)

Couldn't the securelevel shown to a module be a different variable than the
real securelevel? Ie have a function copy the securelevel into a visible
variable, but have the kernel keep it's own copy that actually is used to
determine behavior, (possibly testing to see if the two values disagree)?

Pascal, n.: A programming language named after a man who would turn over in
his grave if he knew about it.

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