Re: [ASLR] Better control on Randomization

[Emmanuel Fleury]

Hi,

Just to say what use I intend to do with this. :)

I'm giving a lecture on software security and I'm trying to have a
kernel in which you can add/remove security features in order to make
the students learn and practice some attacks (this kernel should run
into a UML process).

Ideally, I would like to be able to activate/deactivate (independently):
- Stack randomization
- Heap randomization
- Library randomization
- Non-executable stack

(for the last one, as the kernel will be minimum (No X, no JVM), it
might be easier to NOT consider the trampoline functions).

Well, for now I'm just looking of the _feasibility_ of this idea
(and how hard would it be to make it run in UML).

Any comments or ideas are more than welcome. :)

Regards
-- 
Emmanuel Fleury

That's the whole problem with science. You've got a bunch of
empiricists trying to describe things of unimaginable wonder.
  -- Calvin & Hobbes (Bill Waterson)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/