Hacking [discussion] Why 5.5.x is ready for its Kexploit

[SkittleDash]

Such a hateful word used by society :-(
Im guessing you don't have any friends or family that are "retarded" like I do. But I also understand it's a word that's used blindly without any thought put in to it. Carry on!

Actually I do and I respect them. Remember, this was a troll I was talking too.

 

[jimbo13]

Actually I do and I respect them. Remember, this was a troll I was talking too.

Spoiler

 

[DiscostewSM]

From what I understand, one reason why the 5.5.0 exploit has not been released is because of a rule/guideline made that they will hold off a release until a newer firmware patches the exploit (or areas the exploit works off of). We didn't get the exploit when 5.5.1 released because it was essentially the same with regard to how the 5.5.0 exploit poked around.

 

[iVcU]

 

[joacosur15]

A new update are around the corner for the new mynintendo, wait.. Or buy a new wii u..

 

[ajd4096]

I nominate Vgmoose to broker a crowd funded bounty for the 5.5 Kexploit.

There is more than enough interest to crowd fund a sizable bounty for the exploit, scene kiddies are sitting on it for politics, shits and giggles. Best estimates is around a dozen people have it and that pot wouldn't even need to get up to a grand before one of them decided to cash in. End of the week it would be done.

Make it $2k, and I'll take a week off work and drink beer^W^W find a new exploit just for you.

 

[•Citrus•]

(I can mostly sympathize with this. Much like OP, I don't give two shits about IOSU or Loadiine being compatible with 5.5.1 or anything piracy related)

Are there people that want to develop for the Wii U but are a bit put off by fact that they have to go out and spend $300 on a console that runs an older firmware just to attempt to make a somewhat decent homebrew app? Of course there are. I myself am one of those people.

The overall underlying problem is, however, that homebrew development tools for the Wii U just aren't up to par quite yet. If you look at ctrulib for 3DS homebrew development (https://github.com/smealum/ctrulib) you'll undoubtedly notice that it's a lot more sophisticated than anything we have for the Wii U at this point in time. Most of the current homebrew apps for the Wii U aren't anything that the end-user interacts with on the console (See: Octohax, XCXGekko, gc-to-vpad, Nin-Jecter). People who want to make things such as emulators or small games are pretty much out of luck for the time being since the current homebrew creation tools are... underdeveloped (for a lack of a better term).

Long story short: As a developer interested in getting into Wii U homebrew development, I'm fine with continuing to wait for a kernel exploit if it means we're going to get a decent development environment to go along with it.

 

[NWPlayer123]

I'm fine with continuing to wait for a kernel exploit if it means we're going to get a decent development environment to go along with it.

What would you consider a decent development environment, if I or someone else were theoretically to work on something like that? Question open to anyone

 

[Merzeal]

What would you consider a decent development environment, if I or someone else were theoretically to work on something like that? Question open to anyone

Hykem implied an SDK in his tweet. Not sure what was meant by that. Could just be all the documentation on WiiUbrew or something more.

EDIT: I'm dumb. Something with decent documentation and decently fleshed out libraries, is more important than some over the top environment for development. In my opinion, obviously.

 

[ajd4096]

What would you consider a decent development environment, if I or someone else were theoretically to work on something like that? Question open to anyone

vi, make, and a gdb stub.

 

[codychaosx]

Wasn't gna comment but, @aprilfool is hilarious, awful, and not adding anything valuable.

As far as releasing anything in any major exploit in the modding,hacking, and homebrew scene. I would expect piracy. I for one only want to use this exploit for plundering and booty. Only homebrew that I would ever use would be emulators and backup loaders. Which i currently do on my 5.4 wii u. While my 5.5 just sits. I guess that's actually a fairly valid point that they aren't preventing piracy by holding it.

also

Such a hateful word used by society :-(
Im guessing you don't have any friends or family that are "retarded" like I do. But I also understand it's a word that's used blindly without any thought put in to it. Carry on!

 

[dojafoja]

Retard

You and my 10 year old son would get along well, considering you have the mindset of a child and all. Are your parents aware of your internet usage? I can't imagine the chores you must have to do to earn your internet time. Maybe your parents should take away your power cables like I do with my child so you can't be an obnoxious prick all the time! Carry on!!

 

[CeeDee]

It's rather interesting how we have yet another 3DS kernel exploit, and only a few for Wii U. Huh.

 

[Taleweaver]

It's an interesting thread, @vgmoose. It's clear you've looked at all the angles and bring a clear case here. And after som pondering, I have to agree with you.

Normally, I'd add a few "but..."'s here, but I'm sure you at least considered everything I could say. You already know this situation isn't as much of a choice as it is a dilemma, with arguments for either side of it.
And unfortunately, I don't have nearly enough influence over the ones holding the exploit to make them reconsider their stance. So all I can say is good luck to you. And thanks for the time to write out the post.

 

[brienj]

I've got all the development tools I need by going through the official documents for the official libraries. Problem is, I can't use the sound library, for one example, with just user space, unless I am really doing something wrong, which I don't think so. Getting a handle to sndcore2 results in a mess, and getting a handle to sndcore works, but any attempt to use the library results in a lockup. I could try to use "legal" libraries, but hell, Loadiine GX2 all but copy/pastes the official header files in their source, so ...

 

[Deleted User]

may be a noob question but how would nintendo patch the exploit without it being released?

 

[Masterwin]

Hi all,

I want to sidestep all the drama (not sure if fully possible). I know there are things on the horizon. Everyone knows there are things on the horizon. We can be patient for these things to be completed to their fullest, because we're all big kids here.

What I want to talk about is the objective fact that there are several developers, myself included, that are on 5.5.x and whose homebrew is suffering from a lack of a kernel exploit being made available. Homebrew is advancing more and more, but it's clear that the limits of what can be done in userland are being pushed.

The thing is, yellows8 already (accidentally, as it was believed to be patched) released the browser exploit, which allowed more developers who are on 5.5.x to get into the scene. Continuing to intentionally keep a kernel exploit a secret is preventing these developers from creating new innovative homebrew.

There's the Homebrew Launcher out, which is new and exciting. It's so exciting that I (being on 5.5) had to blindly try to support it.

I don't want to name any other developers, but I want to go on the public record as a dev who is against this blocking on the community. I would love to continue bringing innovation to the homebrew scene, but am finding it very hard to find the inspiration when any homebrew I write is essentially a glorified web app.

I like to keep things open and give back to the community, so I really can't understand the mindset that keeping it private is somehow productive. If it's a matter of being afraid of being sued, I'd like to point out that Sony was not successful with their lawsuit. They settled out of court (read: paid him off to stop *speculation*).

And yes I'm actively researching kernel exploits and trying to find one, but it isn't easy... I've heard @Marionumber1 has given his kernel exploit to some devs, but I'm not interested in being in some exclusive developer club. I am interested in the furthering of the community and the homebrew scene.

I like to control my devices, and I don't like not having control over them. I don't like the reaction that some people have on this forum that all people wanting the kernel exploit are whiny pirate babies.

Nintendo has decided that they decide what people do on their own devices. They've decided this so much to the point that the Wii U's operating system self-updates. As the users, we have the power to take back control. Yes this is a righteous cause, and no we should no condemn people for wanting freedom. (perhaps we can condemn the actually whiny ones though).

As far as I am aware this thread is not against any gbatemp rules. Moderators, if you have an issue with this thread, please let me know so that I can adjust my attitude. But please don't silence it just for being what it is.

Let's have an intelligent discussion about the pros and cons of releasing vs holding onto exploits. To me, it blocks developers from creating content. Nintendo is going to patch in the end if they care enough, no matter what, and there are devs that are ready to advance the scene right now.

I'm very open to hearing other points of view. I'm coming from a background with open source philosophies, so maybe I'm missing something here. I just don't see why this should be a special case.

With much love,
A user

PS: For the record, I am not referring to IOSU at all, but simply the existing, private kexploit for 5.5.

I totally agree with you, and I want you to know that you have my WiiU 5.4E at your disposal to try everything you need, when you need it , a greeting!

 

[Daggot]

may be a noob question but how would nintendo patch the exploit without it being released?

They're probably hoping Nintendo will finally find the flaw themselves and patch it. It could happen but then again it could never happen. From an end user's perspective the only thing to do now is wait.

 

[Deleted User]

They're probably hoping Nintendo will finally find the flaw themselves and patch it. It could happen but then again it could never happen. From an end user's perspective the only thing to do now is wait.

ok thanks

 

[lonelyhero]

may be a noob question but how would nintendo patch the exploit without it being released?

Luck mostly