Hacking Question for Marionumber1 and NWPlayer

[WeedZ]

Actually, it works like this.

There's a 5.5 kernel exploit working and ready for release. The developers are keeping it because Nintendo may not know about the entrypoint/vulnerability.

Now, if Nintendo releases a new firmware, and the entrypoint isn't patched, then the exploit automatically works for that firmware.

If we release it now and Nintendo finds out, they'll patch it. Then, the exploit works only for 5.5 and a new exploit must be found for the next firmware.

What is the best outcome here? If we had two exploits, one would be released and the second would be kept. Easy.

But we only have this one, and it's best to keep it compatible and reliable.

So basically everyone has to do without until someone finds another vulnerability because of idiots that will update their systems. Why are we catering to the lowest common denominator? I say sink or swim.

Not to mention, if it is shared sooner more people would be able to look for other vulnerabilities, or ways to reuse the one we have. Look at the 3ds scene and all the downgrade and entry point methods. Smea didn't make them all. He just shared memchunkhax. Just because a small group of hackers have the ability to control the flow of a particular scene doesn't mean it's a good idea for them to do so. Hacking and politics take two very different skillsets.

 

[LinkMain111]

Do you even know how much effort, work, and luck require research for an exploit?
It's very easy push and complain to be reléase the exploit that so much effort needed and it's easier patch it with a new update firmware by Nintendo.
Just wait or make your own exploit, then you will do the same , you will keep your exploit safe of anything that could ruin your effort

Are you speaking to me,since I never denied any of those things

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

So basically everyone has to do without until someone finds another vulnerability because of idiots that will update their systems. Why are we catering to the lowest common denominator? I say sink or swim.

Not to mention, if it is shared sooner more people would be able to look for other vulnerabilities, or ways to reuse the one we have. Look at the 3ds scene and all the downgrade and entry point methods. Smea didn't make them all. He just shared memchunkhax. Just because a small group of hackers have the ability to control the flow of a particular scene doesn't mean it's a good idea for them to do so. Hacking and politics take two very different skillsets.

Was about to say exactly what you said in the first paragraph.

 

[ajd4096]

Hacking and politics take two very different skillsets.

Which do you have? It's hard to tell from here.

 

[lonemoonHD]

So basically everyone has to do without until someone finds another vulnerability because of idiots that will update their systems. Why are we catering to the lowest common denominator? I say sink or swim.

Not to mention, if it is shared sooner more people would be able to look for other vulnerabilities, or ways to reuse the one we have. Look at the 3ds scene and all the downgrade and entry point methods. Smea didn't make them all. He just shared memchunkhax. Just because a small group of hackers have the ability to control the flow of a particular scene doesn't mean it's a good idea for them to do so. Hacking and politics take two very different skillsets.

I don't understand what you mean by this?

First off, yes, 5.5 homebrew development isn't the prettiest without the kernel exploit, but withholding it is the greater good here; like you said, if some nut updates their FW, he's fucked unless the exploit actually works in the next FW. See the connection? And anyway, people should definitely keep their consoles alone, not updated, and that has been reprised almost a thousand times (maybe far more than that). It's nobody's fault some idiot updates.

Secondly, vulnerabilities can be found anytime by anyone. I'm not denying that. There's just nobody up for the task. Many people have tried to make a 5.5 kexploit, and we've never heard about their progress since. Nobody's "controlling the scene", just make your own working kernel exploit and then maybe you'll take the scene by storm.

Thirdly, releasing it here and now is definitely not logical, because they can patch it, like I said for about the fourth time now. It would also be a little brisk since the exploits are usually expected after the update. The reason for this is because we check if the exploit was patched or not, and if it was, we make a release date. Simple, eh?

 

[Seita]

Someone tell us why N released the last 3 updates?
Wasn't that a response to Loadiine and MP4?
If someone thinks N will update a stable console, they are totally deluded.

 

[moops44]

Someone tell us why N released the last 3 updates?
Wasn't that a response to Loadiine and MP4?
If someone thinks N will update a stable console, they are totally deluded.

maybe they fixed unknown exploits?
i dont think they just sit and watch

 

[Seita]

maybe they fixed unknown exploits?
i dont think they just sit and watch

I think they'really getting smarter with updates. It's as if they let the community release things and act accordingly. They won't patch things no one uses.
Their rational now is nothing exists if not released. A smart move if you ask me.

 

[LinkMain111]

I don't understand what you mean by this?

First off, yes, 5.5 homebrew development isn't the prettiest without the kernel exploit, but withholding it is the greater good here; like you said, if some nut updates their FW, he's fucked unless the exploit actually works in the next FW. See the connection? And anyway, people should definitely keep their consoles alone, not updated, and that has been reprised almost a thousand times (maybe far more than that). It's nobody's fault some idiot updates.

Secondly, vulnerabilities can be found anytime by anyone. I'm not denying that. There's just nobody up for the task. Many people have tried to make a 5.5 kexploit, and we've never heard about their progress since. Nobody's "controlling the scene", just make your own working kernel exploit and then maybe you'll take the scene by storm.

Thirdly, releasing it here and now is definitely not logical, because they can patch it, like I said for about the fourth time now. It would also be a little brisk since the exploits are usually expected after the update. The reason for this is because we check if the exploit was patched or not, and if it was, we make a release date. Simple, eh?

You disregarded all of what he said.

 

[lonemoonHD]

You disregarded all of what he said.

Because I didn't understand him at all

 

[Cava]

Sorry i'm just joking and I'm on 5.3.2 but i can't miss this:

 

[Net-KILLER]

 

[TeamScriptKiddies]

I will not release anything. x----D

Me neither, because legally I can't XD. Of course that's saying I had an exploit to begin with, which I dont

 

[WeedZ]

Which do you have? It's hard to tell from here.

Politics by far

I don't understand what you mean by this?

First off, yes, 5.5 homebrew development isn't the prettiest without the kernel exploit, but withholding it is the greater good here; like you said, if some nut updates their FW, he's fucked unless the exploit actually works in the next FW. See the connection? And anyway, people should definitely keep their consoles alone, not updated, and that has been reprised almost a thousand times (maybe far more than that). It's nobody's fault some idiot updates.

Secondly, vulnerabilities can be found anytime by anyone. I'm not denying that. There's just nobody up for the task. Many people have tried to make a 5.5 kexploit, and we've never heard about their progress since. Nobody's "controlling the scene", just make your own working kernel exploit and then maybe you'll take the scene by storm.

Thirdly, releasing it here and now is definitely not logical, because they can patch it, like I said for about the fourth time now. It would also be a little brisk since the exploits are usually expected after the update. The reason for this is because we check if the exploit was patched or not, and if it was, we make a release date. Simple, eh?

I understand, but your logic is flawed is what I'm saying. Cracking security is not the same as writing software for a known vulnerability. Smea released memchunkhax, and now we have a method for downgrading every 3ds fw. This evolved over time by people that don't know how to find entrypoints on their own, but have manipulated known hacking methods. My point being, it was released and now it doesn't really matter if it's patched through a fw update because the resources to overcome it will always be there. If smea waited for them to patch it, we would STILL be waiting.

By the logic of "wait till nintendo patches it", nintendo has no need to put in the work, pay programmers, or even push an update. Why would they ever spend the money if they know any vulnerability will never be shared with the public?

So really, there is no "greater good". Its, some have to wait it out a bit, or nobody gets anything. And we've seen the benefit of sharing knowledge with the community time and time again. So I don't know where this new mindset comes from.

 

[tech3475]

I think we need a new sub-forum 'WHERE'S MAH HAX!'.

/sarcasm.

Seriously, how many of these kinds of topics have we had now?

 

[nero99]

Wii u scene is dead..like The console itself
Sell It Now And wait for nx

Where's your proof?

 

[KiiWii]

Me neither, because legally I can't XD. Of course that's saying I had an exploit to begin with, which I dont

Have you done anything with your Cat Dev?

 

[WeedZ]

I think people that have an exploitable wiiu shouldn't be allowed to respond to these threads. It easy to say people whine too much when you already have what they want. I also think that people that don't even have a wiiu (me) should get bonus points for being completely objective.

 

[Monado_III]

So couldn't Nintendo just not patch it, even if they found an issue, and viola, no more worrying about someone releasing an exploit? Nintendo would win and, more importantly, the scene would loose.

 

[Donzi]

So couldn't Nintendo just not patch it, even if they found an issue, and viola, no more worrying about someone releasing an exploit? Nintendo would win and, more importantly, the scene would loose.

But then the people on this firmware get the Kexploit. Nintendo are digging their own graves, the longer they leave it, the worse the damage once it comes (since it will be supported on way more versions). As long as we're patient it's a win win.

 

[TheZander]

I think someone needs to make another countdown. Those things tend to make stuff happen.