[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[f-cpu] tlb last ! (secure bit, lib ring)



I forgot to add for the tlb, the tagged region.
- So one more bit in the tlb ("secure bit").
- split the load&store in normal and secure one (to access the secure
area).

Maybe we could have one user secure bit and one superuser secure bit.

[That's mainly to definitely protect the return stack from buffer
overflow. return stack are on a secure area, and buffer are only managed
by normal load&store. Only fonction pointer are now a problem : this
could be solve with the use of a new ring to protect excve ? (that's
means that to access excve a kind of trap must occur which is a very
different thing compare to a typical function call)]

[Maybe rwx right for this new (lib ?) ring could be added, too.]

nicO


______________________________________________________________________________
Pour mieux recevoir vos emails, utilisez un PC plus performant !
Découvrez la nouvelle gamme DELL en exclusivité sur i (france)
http://www.ifrance.com/_reloc/signhdell

*************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/