Difference between revisions of "Talk:3DS System Flaws"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
Yeah, yeah, great hacking plans, kids. What are you going to do once you find a buffer overflow? Blindly write stuff to memory hoping to hit the PICA200 registers someday? Quit wasting your time with buffer overflows. Come back when more is known. --[[User:Luigi2us|Luigi2us]] 20:42, 15 August 2011 (CEST) | Yeah, yeah, great hacking plans, kids. What are you going to do once you find a buffer overflow? Blindly write stuff to memory hoping to hit the PICA200 registers someday? Quit wasting your time with buffer overflows. Come back when more is known. --[[User:Luigi2us|Luigi2us]] 20:42, 15 August 2011 (CEST) | ||
| + | |||
| + | How would you write a 3DS Exploit, Luigi2us? | ||
Revision as of 11:25, 17 August 2011
I have a way to freeze the 3DS which might be exploitable - see Talk:Internet Browser. R4wrz0rz0r 14:59, 20 June 2011 (CEST)
- That crash isn't exploitable unless you're extremely lucky. Don't waste your time. --Luigi2us 20:44, 15 August 2011 (CEST)
It is not so bad to looking for buffer overflow.
But try to know about file system is more important.
And we do not know enough about CCI,... formats to write an exploit with a loader which loads an executable file! Maybe we should try to make a savegame exploit...
Yeah, yeah, great hacking plans, kids. What are you going to do once you find a buffer overflow? Blindly write stuff to memory hoping to hit the PICA200 registers someday? Quit wasting your time with buffer overflows. Come back when more is known. --Luigi2us 20:42, 15 August 2011 (CEST)
How would you write a 3DS Exploit, Luigi2us?