Remembrance protection in the segment organization



  • Hello.

    There's a thing like a buffer refilling: we're wiping the return address in the glass to some other one where the instructions we want to do are set. And most likely to be the address that belongs to the segment of the stem (both or pile). Why is the processor, when EIP indicates an address outside the code segment, doesn't panic or err the segmentation? Isn't that tracked by flagss in segment descriptor?

    http://ru.wikipedia.org/wiki/%D0%A1%D0%B5%D0%B3%D0%BC%D0%B5%D0%BD%D1%82%D0%BD%D0%B0%D1%8F_%D0%B7%D0%B0%D1%89%D0%B8%D1%82%D0%B0_%D0%BF%D0%B0%D0%BC%D1%8F%D1%82%D0%B8 Says there's no such protection, but then there's a reasonable question, why?



  • With regard to the discussion in the commentaries (on the accidental location of the memorial), it may be read http://ru.wikipedia.org/wiki/Address_Space_Layout_Randomization ♪ On the possibility or impossibility of memory, I was curious to read http://ru.wikipedia.org/wiki/PaX ♪ Accidentally, I ran into Casserski. http://www.insidepro.com/kk/063/063r.shtml Now I know a lot of smart words:


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 3
  • 1
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2