Editing Talk:RAM
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 16: | Line 16: | ||
According to a tweet by (already deleted, [https://twitter.com/RichDevX/status/504389462496137217 source]), there is a backdoor in XDR Ram that allows the attacker to write to any place in the memory. 16:40, 27 August 2014 [[User:Zecoxao]] | According to a tweet by (already deleted, [https://twitter.com/RichDevX/status/504389462496137217 source]), there is a backdoor in XDR Ram that allows the attacker to write to any place in the memory. 16:40, 27 August 2014 [[User:Zecoxao]] | ||
: without actual tweet hard to discuss... It is in the nature of /XDR/ RAM to be Random Accessable Memory in the first place ;) As long as you stick to that one module at a time. There is no HV/W^X etc on that hardware level (which takes place in the CPU / OS instead) [[User:Euss|Euss]] ([[User talk:Euss|talk]]) 12:13, 27 August 2014 (EDT) | : without actual tweet hard to discuss... It is in the nature of /XDR/ RAM to be Random Accessable Memory in the first place ;) As long as you stick to that one module at a time. There is no HV/W^X etc on that hardware level (which takes place in the CPU / OS instead) [[User:Euss|Euss]] ([[User talk:Euss|talk]]) 12:13, 27 August 2014 (EDT) | ||