Hacking UPDATE 5. >> 3 << .0

[NWPlayer123]

Note: that new bee is talking about something that can possibly break the in-progress kernel exploit (IDR what the one I'm involved with uses, I'd have to check). I was referring to finding a bug to get code execution back in the first place.

 

[Jackall4BDN]

Damn. Please people keep all the incoming drama to the 3ds forum.

Dalavin comes and writes about closed bug, community goes:

Spoiler: Tragedy

 

[FPSRussi4]

Note: that new bee is talking about something that can possibly break the in-progress kernel exploit (IDR what the one I'm involved with uses, I'd have to check). I was referring to finding a bug to get code execution back in the first place.

But even if this one gets patched, there are others I assume.

 

[digipimp75]

Still hanging on 4.1.0 here. Will continue to be "off the grid" until homebrew is a possibility, however damn long that will be lol

 

[WulfyStylez]

Heyo, just popping in to say that that's a bug we were using. Don't update.

The person who reported that is also probably a nintendo dev for what it's worth. That description was a little too specific for them not to be.

 

[Ray Lewis]

Heyo, just popping in to say that that's a bug we were using. Don't update.

The person who reported that is also probably a nintendo dev for what it's worth. That description was a little too specific for them not to be.

So it is not completed...then the hole being used is patched in 5.3...then there is no public iosu(?) exploit? I am not sure if mine updated to 5.3 yet. Was the Nintendo person sticking up a middle finger? Why stick that message out in the open?

 

[NWPlayer123]

So it is not completed...then the hole being used is patched in 5.3...then there is no public iosu(?) exploit? I am not sure if mine updated to 5.3 yet. Was the Nintendo person sticking up a middle finger? Why stick that message out in the open?

There was never an IOSU exploit in development in the first place (except for Fail0verflow's to get all the keys). But yes, the kernel exploit is now broken as well. Back to square one. At least we learned more about the system ¯\_(ツ)_/¯ Nonetheless, a new one should be in the works by the time Christmas rolls around.
EDIT: That is, unless we decide to finish the first one before making one for the latest version, so we at least have working exploit on SOME versions.

 

[pedrobarca]

Heyo, just popping in to say that that's a bug we were using.

Since the bug this guy talked about was kernel related, does that mean you guys have a working kernel exploit?

 

[FPSRussi4]

There was never an IOSU exploit in development in the first place (except for Fail0verflow's to get all the keys). But yes, the kernel exploit is now broken as well. Back to square one. At least we learned more about the system ¯\_(ツ)_/¯ Nonetheless, a new one should be in the works by the time Christmas rolls around.

Well, why not just keep developing the exploit fully now, then work on porting later? or is this the PS3 issue?

 

[WulfyStylez]

There was never an IOSU exploit in development in the first place (except for Fail0verflow's to get all the keys). But yes, the kernel exploit is now broken as well. Back to square one. At least we learned more about the system ¯\_(ツ)_/¯ Nonetheless, a new one should be in the works by the time Christmas rolls around.

Not back to square one at all. This doesn't affect anyone working on exploit stuff as nobody's really updated.

 

[NWPlayer123]

Since the bug this guy talked about was kernel related, does that mean you guys have a working kernel exploit?

Semi-working. Not actually able to do anything yet.

Well, why not just keep developing the exploit fully now, then work on porting later? or is this the PS3 issue?

That's always an option. Considering we were planning on finishing the kernel exploit and then finding another bug for code execution in the first place, that would probably be wise.

 

[Hykem]

-Deleted-

 

[FPSRussi4]

Semi-working. Not actually able to do anything yet.

That's always an option. Considering we were planning on finishing the kernel exploit and then finding another bug for code execution in the first place, that would probably be wise.

Hey, thanks. It just makes more sense; Nintendo will keep pushing updates no matter what you guys do, and we can wait. Worst case scenario: it's the PS3.

 

[Jackall4BDN]

I´m gonna start regretting updating some hours ago as soons as actual usable game-mods or something in that manner come out (like ProjectM4 or CTGPR8) , until then i´m going to be fine with it, i guess.

 

[the_randomizer]

I'm so lost, I've been gone for an hour and I don't know what just happened

 

[FPSRussi4]

I'm so lost, I've been gone for an hour and I don't know what just happened

TL, DR Don't Update.

 

[the_randomizer]

TL, DR Don't Update.

Hmm, I just received a cryptic message from....anyways. Doesn't SSB4 have 5.3.0 on the disc though?

 

[zecoxao]

so, there's a fix from nintendo on an exploitable kernel bug... alright i guess

 

[the_randomizer]

so, there's a fix from nintendo on an exploitable kernel bug... alright i guess

Why are you congratulating on Nintendo fixing a bug on a hacking thread?

 

[Jackall4BDN]

Why are you congratulating on Nintendo fixing a bug on a hacking thread?

Should he be writing a support-mail? xDD