Hacking Why you deserve a 5.5 kernel exploit, but also why you can't have one

MrDanny

Member
OP
Newcomer
Joined
Apr 11, 2016
Messages
9
Trophies
0
XP
70
Country
Albania
So a lot of people here seem to fall into two categories:
- shaming developers who don't release exploits, call them childish
- shaming people who want a release (whiners), call them childish

And I think we've got a bit of this going on: http://www.smbc-comics.com/?id=2939

That is, outside of the loud, obnoxious people, there are valid opinions that can be had here. Yet due to those very people, both sides view the other side as somewhat toxic.

There's two worlds:

1. Exploit is released to the public

Pros:
- People can use the exploit on at least 5.5.1
- Developers without the exploit can use it to develop homebrew/wii u sdk apps
- Developers interested in exploiting can learn from it and potentially help exploit in the future
- Kernel homebrew can be run on store-bought Wii U's
- Builds the "community"

Cons:
- Nintendo would definitely have the exploit and could patch in a future release
- It's been held private for this long, might as well keep waiting (don't make the waiting pointless)


2. Exploit is kept private until another exploit is public

Pros:
- The (rumored to be very stable) kernel exploit can be used in the future
- With a future deeper exploit (such as IOSU) it would be very useful to have a stable kernel entrypoint
- People who are "in the know" can technically request access to further their understanding now
- Nintendo can't easily patch it if it's not released
- Potentially builds the long-term "community"

Cons:
- If a new private exploit came about and followed this same logic, neither would be public
- Latest Wii U firmware is not exploitable
- Developers who could request access might not want to, as they would prefer it be available to all


Assumptions made:
- There is only one 5.5.1 kernel exploit that works
- That exploit is stable
- That exploit would be perfect for deeper level playing later
- Nintendo would actively patch the exploit


These are not the only arguments that can be made, and there are surely more factors at work here. These are some of the most popular "valid" points that I've seen be made by both sides.

I'd like this thread to be an argument. But I'd also like the argument to focus solely around these pros/cons/assumptions (or new VALID ones). No whining or calling the other side childish. I have the impression that a lot of developers that have the kernel exploit are more quiet than not quiet because anything that they say can be a lightning rod for flamers. This is a "safe space" in that regard. But please, let your opinion be known.
 

AmandaRose

Do what I do. Hold tight and pretend it’s a plan
Member
Joined
Aug 19, 2015
Messages
10,197
Trophies
1
Location
Glasgow
Website
www.rockstarnorth.com
XP
16,167
Country
United Kingdom
So a lot of people here seem to fall into two categories:
- shaming developers who don't release exploits, call them childish
- shaming people who want a release (whiners), call them childish

And I think we've got a bit of this going on: http://www.smbc-comics.com/?id=2939

That is, outside of the loud, obnoxious people, there are valid opinions that can be had here. Yet due to those very people, both sides view the other side as somewhat toxic.

There's two worlds:

1. Exploit is released to the public

Pros:
- People can use the exploit on at least 5.5.1
- Developers without the exploit can use it to develop homebrew/wii u sdk apps
- Developers interested in exploiting can learn from it and potentially help exploit in the future
- Kernel homebrew can be run on store-bought Wii U's
- Builds the "community"

Cons:
- Nintendo would definitely have the exploit and could patch in a future release
- It's been held private for this long, might as well keep waiting (don't make the waiting pointless)


2. Exploit is kept private until another exploit is public

Pros:
- The (rumored to be very stable) kernel exploit can be used in the future
- With a future deeper exploit (such as IOSU) it would be very useful to have a stable kernel entrypoint
- People who are "in the know" can technically request access to further their understanding now
- Nintendo can't easily patch it if it's not released
- Potentially builds the long-term "community"

Cons:
- If a new private exploit came about and followed this same logic, neither would be public
- Latest Wii U firmware is not exploitable
- Developers who could request access might not want to, as they would prefer it be available to all


Assumptions made:
- There is only one 5.5.1 kernel exploit that works
- That exploit is stable
- That exploit would be perfect for deeper level playing later
- Nintendo would actively patch the exploit


These are not the only arguments that can be made, and there are surely more factors at work here. These are some of the most popular "valid" points that I've seen be made by both sides.

I'd like this thread to be an argument. But I'd also like the argument to focus solely around these pros/cons/assumptions (or new VALID ones). No whining or calling the other side childish. I have the impression that a lot of developers that have the kernel exploit are more quiet than not quiet because anything that they say can be a lightning rod for flamers. This is a "safe space" in that regard. But please, let your opinion be known.
The thing is the people behind the exploit for wiiu won't bring it out until Nintendo brings out new firmware so what reason does Nintendo have to bring out new firmware the answer is they have absolutely no reason to bring out new firmware when the latest one is safe because the hack developers won't bring out the exploit until Nintendo update it.
 

MrDanny

Member
OP
Newcomer
Joined
Apr 11, 2016
Messages
9
Trophies
0
XP
70
Country
Albania
The thing is the people behind the exploit for wiiu won't bring it out until Nintendo brings out new firmware so what reason does Nintendo have to bring out new firmware the answer is they have absolutely no reason to bring out new firmware when the latest one is safe because the hack developers won't realise it until Nintendo update it.
I left this out because I think that the fact that there's going to be release if a new firmware hits seems like speculation to me. I think they want that "deeper" exploit, whether it's on this firmware or a newer one.
 
  • Like
Reactions: AmandaRose

AtlasFontaine

Well-Known Member
Member
Joined
Jul 18, 2015
Messages
1,095
Trophies
0
Age
26
Location
Venezuela-Zulia.
XP
865
Country
Venezuela
At this point, I believe the kernel exploit will be released at the end of WiU life cycle since NX is on the way, and by that time there probably won't be people interested in the WiiU so it will be kinda pointless.

It seems like nintendo is aware that Devs want them to fix the exploit to release it so they aren't going to fix it on purpose. So its fair to say that the WiiU homebrew scene is pretty much dead.
 
Last edited by AtlasFontaine,

Supster131

(づ。◕‿‿◕。)づ *:・゚✧
Member
Joined
Jan 19, 2016
Messages
3,315
Trophies
1
Location
My Computer
XP
2,758
Country
United States
Why do you think the exploit has remained private for months? :P
Well, with that logic, practically no exploit ever would ever be released before a console is dead...
As some people have stated, Nintendo isn't really bothering that much with the Wii U. The Wii U was technically a flop for them. Nintendo's probably putting all their work and effort to the NX, to make it a good and secure console. The Wii U hasn't had an update for like what, 3-4 months? Compare that to the 3DS, last update that got was probably a little over a month.
 

Ratatattat

Well-Known Member
Member
Joined
Mar 16, 2016
Messages
236
Trophies
0
XP
495
Country
United States
Your wasting your time. Such ideas are not allowed. This thread will soon be locked. I know, I said basically the same thing in a thread I started. And it got locked.
 
  • Like
Reactions: Subtle Demise

Kafluke

Well-Known Member
Member
Joined
May 6, 2006
Messages
5,474
Trophies
0
Age
47
XP
4,636
Country
United States
Your wasting your time. Such ideas are not allowed. This thread will soon be locked. I know, I said basically the same thing in a thread I started. And it got locked.
That's because everything that you and this OP said have been said over and over again. They don't lock threads unless it's useless BS. What was the point of this thread? Did you hope it would spur the devs to release the kexploit? Not likely. Did you hope that it would prevent others from making the same useless whining thread? You only contributed to the problem. This topic is debated constantly on here derailing other useful threads. Don't make another thread yet again with the same BS we've all heard over and over.
 

Jayro

MediCat USB Dev
Developer
Joined
Jul 23, 2012
Messages
12,995
Trophies
4
Location
WA State
Website
ko-fi.com
XP
17,046
Country
United States
All I hear is a whole lot of people talking, people talking about people talking and nobody doing.
Exactly. It's fine if someone makes it for their personal and won't release it, but don't brag that you have one when you won't release it, just to be a dick about it to those of us waiting.
 
  • Like
Reactions: lefthandsword

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    NinStar @ NinStar: the voices inside my head