Accessing USB itself isn't the problem I don't think. As you said, there are games that have access other ways like the skylander pads, gamecube adapter etc. The problem is the USBSTORAGE class is locked out I believe, which is why we need IOSU.
yeah i meant direct usbstorage access not just any old usb accessory,
The IOSU vulnerabilities we're looking at (there are two) should likely work up until 5.5.0. However, the 5.4.0/5.5.0 userspace exploit is still unreleased, and even if they were, the 5.5.0 PPC kernel exploit is even more private, and the IOSU exploits rely on it.
just to clarify, do they rely on that kernel exploit specifically or would it also work with the current public kernel exploits on 5.3.2?
Any PPC user or kernel exploit that we make is designed to function the same way, and thus be interchangeable. So they would work with the OSDriver exploit, the private 5.5.0 one, or kernel exploits that have been discovered but unimplemented (there is at least one).
yeah that what i thought, it just sounded like maybe it was dependent on that specific exploit
Still no hope for the unstable 5.4.0 userspace exploit ?
PPC userspace exploits have regrettably taken a backseat to the more interesting work of IOSU exploitation. We'll get to it eventually.
Yeah we hoped we coud at least enjoy what the scene has for now till the IOSU comes out :S. Especially that the bug is public now. But anyway, thanks for all the effort you guys are doing, keep it upPPC userspace exploits have regrettably taken a backseat to the more interesting work of IOSU exploitation. We'll get to it eventually.
D
Deleted-355425
Guest
Hahah yea, the xbox 360 had some pretty impressive security... Apart from being able to activate JTAG on older xbox's, the security were wild from a software point-of-view. However, even the exploit found there, was unable to be completely patched away by them (as it lied in the processor-architecture (= how it handled pulses on the RST pin of different lengths))
Also, I would definitely not say the security of the PS3 was botched. After all, despite the mistake in the signing of their firmware being huge, it after all took 4(ish?) years to break that security, which made the PS3 the longest-lasting non-jailbroken console of the last generation
Honestly, regardless of how big the mistake on Sonys part were (it was (very) big), I still consider the feat by fail0verflow of finding that flaw in the crypto and mapping the PS3 system and chain-of-trust, as one of the most impressive done on the PS3 scene (ECDSA is state-of-the-art cryptology, they just implemented it wrong)...
The counter by Sony (moving everything from the metldr to lv0) was nicely thinking as well
Note: Yes, that makes me moist as well :3
Edit: Those e-fuses was pretty crazy
...Something cool came out of the spareparts though! http://www.se7ensins.com/forums/thr...0-controller-wireless-receiver-for-pc.668839/
I can now connect xbox controllers to my PC wirelessly! Each time me and my friends plays Mario Party 3 on an emulator, we do that
The latest 360 cant be hardmodded yet, winchester
So what are the chances, given the knowledge gained about Kernel/IOSU exploit level, for a 3DS style emuNAND, i.e. the Wii U (on a lower fully exploitable FW) semi-boots the official current FW where patches are applied in RAM (so no exploit for that FW is necessary as that gets patched in RAM before contol is passed to it)?
The idea is of course to keep the exploitable FW in SysNAND, with Internet disabled, then reboot into emuNAND with Internet enabled. With new3DS this is not possible anymore starting FW 9.6.0 because of an extra key. Anyone know if Wii U can implement something similar?
The idea is of course to keep the exploitable FW in SysNAND, with Internet disabled, then reboot into emuNAND with Internet enabled. With new3DS this is not possible anymore starting FW 9.6.0 because of an extra key. Anyone know if Wii U can implement something similar?
I don't understand you guys, why are you keeping the exploit private? Isn't the bug public? Nintendo will patch the exploit sooner or later! So why? It'll only get users angry.PPC userspace exploits have regrettably taken a backseat to the more interesting work of IOSU exploitation. We'll get to it eventually.
I think I know what Nintendo is thinking of: if we don't patch their exploit, they'll just keep it private, MWAHAHA!
I don't understand you guys, why are you keeping the exploit private? Isn't the bug public? Nintendo will patch the exploit sooner or later! So why? It'll only get users angry.
I think I know what Nintendo is thinking of: if we don't patch their exploit, they'll just keep it private, MWAHAHA!
Even though how we feel about it is irrelevant since we aren't paying for their work or anything, still I would really appreciate it if they released it this time, I understand they said it's too unstable it will actually just get users more frustrated, but seeing how much work done on the last exploit and how it got improved since it's release, there is a good chance this one will be improved too once it comes out ^^.
Eventually once IOSU is done the main developers may get the time to improve it themselves too. At least before that time we with this awkward firmware 5.4.0 can have something to mess with ! XD
And yeah I thought on myself too maybe nintendo's decision on not releasing a firmware yet is probably influenced by the devs decision here ^^. That probably just shows the devs still have the upper hand.
A public exploit will likely trigger a patch-response faster from ninty than a closed one would. Whether the bug or not is public comes second in their eyes to if it is a bug being used.I don't understand you guys, why are you keeping the exploit private? Isn't the bug public? Nintendo will patch the exploit sooner or later! So why? It'll only get users angry.
I think I know what Nintendo is thinking of: if we don't patch their exploit, they'll just keep it private, MWAHAHA!
Can you tell me what are the advantages of the exploit being patched slowly? It'll only make users wait longer.
That's why I said nin will patch it sooner or later, so there's no point of keeping the exploit private.
Last edited by AboodXD,
more firmware exploitationCan you tell me what are the advantages of the exploit being patched slowly? It'll only make users wait longer.
That's why I said nin will patch it sooner or later, so there's no point of keeping the exploit private.
- Joined
- Nov 26, 2012
- Messages
- 2,567
- Trophies
- 2
- Location
- United States
- Website
- sites.google.com
- XP
- 3,880
- Country
As time goes onm we get more firmware version.
If we wait a year for firmware exploit, we get a year of exploitable Wii Us, and so more people can use the exploit.
Similar threads
