Hacking What is stopping us from hacking into the ISOU using the Kernel exploit?

  • Thread starter Thread starter Goopyjoe
  • Start date Start date
  • Views Views 16,985
  • Replies Replies 106
no it isn't. we need an exploit into the IOSU. we already have the kernel exploit, and then, when we will find an IOSU exploit, we will use the ernel exploit to boot the iosu exploit (i think)
 
no it isn't. we need an exploit into the IOSU. we already have the kernel exploit, and then, when we will find an IOSU exploit, we will use the ernel exploit to boot the iosu exploit (i think)

Well yeah, but couldn't someone just code up an app that you run from the Kernel exploit that turns off/disables the ISOU?
 
Well yeah, but couldn't someone just code up an app that you run from the Kernel exploit that turns off/disables the ISOU?
*Facepalms*
:hateit: <- my phone

--------------------- MERGED ---------------------------

Ya expect like a dozen of this same comment. Great community eh? I don't know much either was curious so I popped in.
It just pisses me off that noobs like these clutter the temp with useless threads asking dumb questions like these. There is a stickied noob question thread.
 
  • Like
Reactions: Luglige
Ya expect like a dozen of this same comment. Great community eh? I don't know much either was curious so I popped in.
one thing is asking what is an exploit. another thing is basically saying "ehhh but it is easy you can do it this way ehhh" withouth knowing of what you are talking about

--------------------- MERGED ---------------------------

PLEASE Never ask when something will be done. "IT WILL Be DONE WHEN IT IS DONE!" That is very rude to ask about and unless your gonna contribute something to the project, there no point in asking that question, when it is done, i'm sure you will know about it.
he ddidn't asked that
 
Well yeah, but couldn't someone just code up an app that you run from the Kernel exploit that turns off/disables the ISOU?
PLEASE Never ask when something will be done. "IT WILL Be DONE WHEN IT IS DONE!" That is very rude to ask about and unless your gonna contribute something to the project, there no point in asking that question, when it is done, i'm sure you will know about it.
 
if i understood it right,
stage1: code excecution (homebrew).
stage2: adding your OS (kernel).
stage3: cracking the faking/patching the sgnatures so that the anti pirate mechanisms wont get alarmed (backuploader/cfw).
stage4: reverse enginering all hardware drivers (as close to the way the original drivers function as it was original done just now for your own OS) (IOSU).
could be getting it wrong though, but if it's as straight forward as i understand... then hell we're not even close of getting there.
 
one thing is asking what is an exploit. another thing is basically saying "ehhh but it is easy you can do it this way ehhh" withouth knowing of what you are talking about

--------------------- MERGED ---------------------------


he ddidn't asked that
It could have gotten to that point. Just being sure it doesn't. :unsure:
 
I'm simply asking what is blocking us from accessing the ISOU.

Well, a lot of stuff actually. I mean the developers spent a lot of time putting in security measures to make sure that nobody can get access to things they are not supposed to. Kernel and IOSU are completely different things.
 

Site & Scene News

Popular threads in this forum