SX OS 2.6 Beta released: full support for Nintendo Switch firmware 7.x
From Team Xecuter:
Download here: -REMOVED-
Download here: -REMOVED-
Last edited by linuxares,
https://twitter.com/balika011/status/1107748638095220738?s=19
Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."
Somebody can explain?
Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."
Triszka Balázs says:
"There is more to the story, and this is gonna be EPIC! They store the root key in plaintext, but they are not using it. On 7.0+ they set the tsec_root_keys + 0x10 then don't even touch it. It's a leftover. What they are using is a seed decrypted using slot 7. That they not clear."
Somebody can explain?
Mike Heskin says:
"This means the plaintext key was left by accident and there was already a system in place to use an obfuscated version. As of v2.6.1, the plaintext key is no longer present in the binary and the obfuscated path is taken just like before."
Last edited by oblid,
Basically they left the key in plain-text out of oversight/rush, and it was in no capacity used (in its plain-text form, just loaded) much like the code remnants of sept, though those still seem to have been left over. It has been removed in plaintext from the boot, and the method is an obfuscated use of seed slot 7 as balika points out.
Last edited by V-Temp,
I’m pretty sure they still have the key in it, it’s just obfuscated/hidden now
(at least that’s how I read hexkyz’s tweet)
And even if the key is completely removed there’s still other stuff in it that makes it violate this website’s rules
(at least that’s how I read hexkyz’s tweet)
And even if the key is completely removed there’s still other stuff in it that makes it violate this website’s rules
Last edited by ZachyCatGames,
Yes... You are right. Balázs and Heskin? Who know them...
Like before? Before that 2.6? 2.5.3 was ok by gbatemp.
And the censorship of link come for keys. Already say that 2.5.3 was ok.
Last edited by oblid,
What happens is that a key is set in keyslot 7 at the end of payload_98000000 and then patcher_BFC70000 does:
- Initialize tmp_buf as 16 0xAA bytes;
- Call se_aes_ecb_decrypt_block(0x07, tmp_buf, 0x10, seed_buf, 0x10);
- Call decrypt_data_into_keyslot(0x0C, 0x07, seed_buf, 0x10).
The se_aes_ecb_decrypt_block is useless and was likely there just for testing (it's still there on v2.6.1 and you can find it by looking for 0xAAAAAAAA in the disassembled code).
This was already being used in v2.6, but they also had a piece of code that would load the actual plaintext key from memory. On v2.6.1 the key and this leftover code was removed.
The user @Falo has shared an accurate screenshot comparison of v2.6 vs. v2.6.1 here: https://gbatemp.net/threads/sx-os-2...license-activation.533956/page-3#post-8559251
Depends on what pretend lawyer they are listening to really. Its still a DMCA violation, but then admitting that would remove links to a few favoured projects.
Similar threads
-
The Real Jdbye
*is birb*
-
@
Psionic Roshambo:
So my opinion is that they could age a bit better in the future, and maybe AMD will continue improving them via drivers like they tend to do. No guarantee there but they have done it in the past. Just a feeling I have. -
-
-
-
@
The Real Jdbye:
they definitely will age better but i feel dlss might outweigh that since it looks about as good as native resolution and much less demanding+1
-
-
@
The Real Jdbye:
AMD could introduce something comparable to DLSS but nvidia's got a lot more experience with that
-
@
The Real Jdbye:
least amd 7xxx has tensor cores which the previous generations didn't so there is the potential for AI upscaling
-
-
-
-
-
-
-
@
The Real Jdbye:
i think i heard of that, it's a good idea, shouldn't need a dedicated GPU just to run a LLM or video upscaling
-
-
-
@
BakerMan:
Have you ever been beaten by a wet spaghetti noodle by your girlfriend because she has a twin sister, and you got confused and fucked her dad? -
-
@
Psionic Roshambo:
I had a girlfriend who had a twin sister and they would mess with me constantly.... Until one chipped a tooth then finally I could tell them apart.... Lol
-
@
Psionic Roshambo:
They would have the same hair style the same clothes everything... Really messed with my head lol
-
@
Psionic Roshambo:
@The Real Jdbye, I could see AMD trying to pull off the CPU GPU tandem thing, would be a way to maybe close the gap a bit with Nvidia. Plus it would kinda put Nvidia at a future disadvantage since Nvidia can't make X86/64 CPUs? Intel and AMD licensing issues... I wonder how much that has held back innovation.
-
-
-