http://danielmiessler.com/blog/security-os-x-leopard-does-memory-randomization grep understanding Fri, 25 May 2012 02:15:50 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://danielmiessler.com/blog/security-os-x-leopard-does-memory-randomization/comment-page-1#comment-242144 Mike Thu, 07 May 2009 19:56:51 +0000 http://dmiessler.com/blogarchive/security-os-x-leopard-does-memory-randomization#comment-242144 <p>Mac OS 9 and before had that "feature" in order to handle all the GUI interfaces elements in limited memory. Handles were pointers to pointers, reason being the memory blocks had to be moved around to make space. You locked a handle before access and unlocked it afterwards.</p> Mac OS 9 and before had that “feature” in order to handle all the GUI interfaces elements in limited memory. Handles were pointers to pointers, reason being the memory blocks had to be moved around to make space. You locked a handle before access and unlocked it afterwards.

]]> http://danielmiessler.com/blog/security-os-x-leopard-does-memory-randomization/comment-page-1#comment-241623 Mike Thu, 07 May 2009 15:56:51 +0000 http://dmiessler.com/blogarchive/security-os-x-leopard-does-memory-randomization#comment-241623 <p>Mac OS 9 and before had that "feature" in order to handle all the GUI interfaces elements in limited memory. Handles were pointers to pointers, reason being the memory blocks had to be moved around to make space. You locked a handle before access and unlocked it afterwards.</p> Mac OS 9 and before had that “feature” in order to handle all the GUI interfaces elements in limited memory. Handles were pointers to pointers, reason being the memory blocks had to be moved around to make space. You locked a handle before access and unlocked it afterwards.

]]>