- Joined
- Apr 29, 2011
- Messages
- 31,284
- Trophies
- 2
- Age
- 38
- Location
- Dr. Wahwee's castle
- XP
- 18,969
- Country
Apparently it was talked about at CCC but I must have missed that
Yeah, know one seems to know what it was, no one even mentioned it.
Apparently it was talked about at CCC but I must have missed that
We didn't know about smhax until that was patched. They usually try to keep things on the downlow until it gets patchedYeah, know one seems to know what it was, no one even mentioned it.
If you keep updating you won't be able to be in the scene. 4.1.0 is confirmed to have cfw being made with an updateable emunand. Unless you want hardmod at this point you can't really be in the scene.
For those wondering:
The Switch's GPU includes a separate MMU (GMMU) that is allowed to bypass the system's IOMMU (SMMU). By accessing the GPU's MMIO region and manipulating the page table entries in the GMMU, an attacker can read/write any portion of the DRAM (except memory carveouts).
[5.0.0+] Works around this hardware flaw by using memory pool partitioning. You can no longer escalate into sysmodules with GPU DMA because all their memory is allocated using heap that's carved out.
We didn't know about smhax until that was patched. They usually try to keep things on the downlow until it gets patched
And literally no one but a select few knew there even was an exploit for this
So yeah, being kept in the dark makes it hard to stay up to day. I think there should be more open sharing of info in the Switch scene.
Different devs do things differently. The ones keeping things quiet are usually not the ones posting videos.I feel like its give and take. If they dont want to be hounded about their exploits and really want to keep things private then don't make YouTube videos bragging about what they have done. Truly keep it to yourself and decide if you want to release or not. If you post proof, expect the outcome. If you get pissed at people for hounding you then its your fault for posting about it. Choices have consequences
Except if they are more open about exploits, those exploits get patched faster. You never seem to understand that they keep these things in the dark for the better good of the community and potentially longer lasting exploits across more firmwares.
How would someone be disappointed by this? This would only be good news unless you updated, because it means more exploits. But if you updated to 5.0.0 then you don't care what the devs say anyway because they've been saying to not update since the beginning.Then maybe it's best to keep expectations in check and remain neutral so we don't end up having any expectations at all. Neutrality has its benefits; you don't get let down or disappointed as much.
How would someone be disappointed by this? This would only be good news unless you updated, because it means more exploits. But if you updated to 5.0.0 then you don't care what the devs say anyway because they've been saying to not update since the beginning.
Ps3. Yeah it got hacked, but it was years later when the console stopped being relevant. It's not impossible, but the likelihood of it happening during the consoles relevancy is low, and that's when most people would want to use homebrew.Look, while I agree with your sentiments and am not updating my consoles barring my main one, the same thing was permanently said about the 3ds all the way along. Where there is firmware, there is bugs. I'm not saying that the switch is necessarily the same, but throughout history there's been a lot of "do not go past this"and then past it ended up being fine down the track.
We've seen what happens when they merely say "don't update" without showing that something is in the works. People update anyway because they feel nothing is coming soon, and then the exploit ends up coming out much sooner and leave people upset that they update.I'm not on 5.0.0, I'm just saying that maybe they should at least release the exploits when they're good and ready, and still tell people not to update anyway, and once done, release it and avoid any teasing. Why can't they do that instead?
We've seen what happens when they merely say "don't update" without showing that something is in the works. People update anyway because they feel nothing is coming soon, and then the exploit ends up coming out much sooner and leave people upset that they update.
Whenever there's a hack for the Switch it is likely to be on a non-current firmware. If you are always up-to-date you'll always miss out. Maybe soon there will be something for 4.1 and you'll miss out, then later there will be something for 8.3 but the latest will be 9.0 etc etc. You'll probably be waiting a couple of years for the Switch to have a hack on the latest version, if the 3DS is anything to go by (briefly there were hacks on latest firmware at 9.2 and 10.3 etc but only for a couple of weeks each time)Look, while I agree with your sentiments and am not updating my consoles barring my main one, the same thing was permanently said about the 3ds all the way along. Where there is firmware, there is bugs. I'm not saying that the switch is necessarily the same, but throughout history there's been a lot of "do not go past this"and then past it ended up being fine down the track.
How switch dev has worked so far, exploits don't release until after they have been patched. So if someone always updates, they'll never have exploits because those exploits that release are already patched. The only thing that would save anyone updating would be a hardware bootrom exploit.Whenever there's a hack for the Switch it is likely to be on a non-current firmware. If you are always up-to-date you'll always miss out. Maybe soon there will be something for 4.1 and you'll miss out, then later there will be something for 8.3 but the latest will be 9.0 etc etc. You'll probably be waiting a couple of years for the Switch to have a hack on the latest version, if the 3DS is anything to go by (briefly there were hacks on latest firmware at 9.2 and 10.3 etc but only for a couple of weeks each time)
More stability?Lmfao you losers still upset about 5.0.0? I'm chillin here on 6.0.0