Hacking Speculations about Switch 2 hacking

  • Thread starter Thread starter KeeperCP1
  • Start date Start date
  • Views Views 381,061
  • Replies Replies 1,088
  • Likes Likes 11
we all saw what sony brought to themselves with no disk policy, nintedo is due for a surprise :P
Sony brought nothing to themselves except that 350,000 PS5 owners out of 99 million whined incessantly about it on their Youtube channels. Did not affect Sony's earnings, stock price or future earnings estimates, which is all Sony cares about and is why they didn't reverse course. It's now a forgotten footnote in their corporate history.

Thanks to GTA6, Sony now cannot make ludicrously-expensive PS5s and PS5 Pros fast enough to meet demand, which will only increase next month making Gameslop's current $1400 price for a beat-up PS5 Pro seem like a bargain. So much for the incelgamerboycott of Sony. 😋

There will be no surprise for Nintendo either. Sorry. Keep dreaming. S2 will not be hacked.
Post automatically merged:

And how many of those pages are just you saying this same thing? It's tiring.

Thing is, I agree with you. I don't think that the switch 2 will be hacked, at least not for a very long time. I think it's interesting to keep up to date with the things people try in order to make it happen, even though I don't think that they're going to succeed. But I feel zero need to announce this fact at every opportunity. I wish that you would do the same, but considering that you've been doing this for a year already, I know that the chances of this happening are slim to none.
Glad you enjoyed my contributions to this thread. They certainly were more entertaining than yours, I'm sure you'll agree. It's interesting that you don't feel the same way about the tiring posts from the same people claiming "nothing is unhackable" like it's their mantra or that if they say it enough times the Switch 2 will bow to them and spill it's keys.

And if you do not want to see me rub their noses in it again and again over the coming year(s), I suggest you use the "ignore" feature that anyone else would use here rather than spewing on needlessly in a post that adds absolutely nothing to this thread. But I know the chances of this happening are slim to none because you, like so many of the haters here, live for my posts.
 
Last edited by ChibiMofo,
Switch 2 has post-quantum cryptography. It uses a quantum-secure signature scheme (XMSS) in early boot chain.

https://switch2brew.org/wiki/BCT
Fernando, it will be defeated by some random, bored early 20's hobbyist no matter how hard you try to damage control. I'm sorry. Someone will be crazy enough not to claim the bounty. This sort of thing has happened before.
mLthB34.png
​
Sony brought nothing to themselves except that 350,000 PS5 owners out of 99 million whined incessantly about it on their Youtube channels. Did not affect Sony's earnings, stock price or future earnings estimates, which is all Sony cares about and is why they didn't reverse course. It's now a forgotten footnote in their corporate history.

Thanks to GTA6, Sony now cannot make ludicrously-expensive PS5s and PS5 Pros fast enough to meet demand, which will only increase next month making Gameslop's current $1400 price for a beat-up PS5 Pro seem like a bargain. So much for the incelgamerboycott of Sony. 😋

There will be no surprise for Nintendo either. Sorry. Keep dreaming. S2 will not be hacked.
Post automatically merged:


Glad you enjoyed my contributions to this thread. They certainly were more entertaining than yours, I'm sure you'll agree. It's interesting that you don't feel the same way about the tiring posts from the same people claiming "nothing is unhackable" like it's their mantra or that if they say it enough times the Switch 2 will bow to them and spill it's keys.

And if you do not want to see me rub their noses in it again and again over the coming year(s), I suggest you use the "ignore" feature that anyone else would use here rather than spewing on needlessly in a post that adds absolutely nothing to this thread. But I know the chances of this happening are slim to none because you, like so many of the haters here, live for my posts.
You need something fun to do. I am trying to read this thread and all of this type of off-topic shit clutters it up.
 
Last edited by doub1eVision,
Fernando, it will be defeated by some random, bored early 20's hobbyist no matter how hard you try to damage control. I'm sorry. Someone will be crazy enough not to claim the bounty. This sort of thing has happened before.
nah, for this specific thing he's right, it wont be broken.
you can review the leaked source code for the entire nvidia chain for t239(switch2)/t234, and basically, even if you worked for nvidia, and had access to the not-included- secret share, each private key requires an additional unique password even if you somehow did have access to it, to even compile the projects in the leak. They made sure that no one except the people in need of know, even if they gained access, had to go through an additional layer. (specifically the binary called siggen, which there are prod signed binaries for t239 in the leak btw which is switch2 exclusive, for nvboot, and riscv security co-processor images, etc, not that any of that is interesting, as they are encrypted by the derived tsec key seed for the t239 which isn't the same as the one for t210 )

the only plausible vector for this directly would be someone working at nvidia, and due to the constraints, that is never happening.

if there's a bootrom bug it won't have anything to do with attacking the signature encryption scheme, and would be a bypass (you are more likely to see userland exploit due to lessons they learned from t210)
 
Last edited by bth,
Fernando, it will be defeated by some random, bored early 20's hobbyist no matter how hard you try to damage control. I'm sorry. Someone will be crazy enough not to claim the bounty. This sort of thing has happened before.
mLthB34.png
​

You need something fun to do. I am trying to read this thread and all of this type of off-topic shit clutters it up.
What will your excuse be in a couple of years?
 
you can review the leaked source code for the entire nvidia chain for t239(switch2)/t234
You are aware that NVIDIA uses ARM-based CPU architectures and that ARM CPU designs can be licensed and examined in extensive detail, right? These architectures have been thoroughly evaluated by numerous major companies, including those you trust with your most sensitive data.

Nevertheless, numerous ARM-based devices have been successfully reverse-engineered and compromised (even on hardware level). Just because certain parts of a system have been publicly leaked does not make it unhackable. If anything, access to such information can make it easier to identify and exploit potential vulnerabilities, even if some people claim that the code is flawless and completely secure. Just because you can identify wrong behaviour in non leaked sources much easier and find an entrypoint somewhere else.

But there is little point in arguing about this here anyway. Some people have seemingly internalized the Roman phrase "Carthago delenda est" to such an extent that they endlessly repeat "It will never be hacked" like some sort of religious mantra, apparently believing they are contributing something valuable to the discussion. They do not even seem to realize how incredibly annoying this constant repetition has become and ignore all facts around them like good internet trolls. At this point, discussing the subject with them feels a lot like arguing with a flat-earther.

What we know so far is that there are multiple entry points, data extraction is possible, and dumps already exist. Furthermore, several individuals with technical expertise far beyond my own have indicated that there are some promising approaches worth investigating. On top of that, we now have AI systems capable of identifying security vulnerabilities at an unprecedented scale, almost like finding candy on Easter. At the same time, we are dealing with a console that offers relatively little incentive for researchers to publicly disclose their findings.

For these reasons, I believe we should limit discussions to publicly available information and actual releases. We should avoid sharing internal details or creating false expectations, but we should also stop endlessly repeating "impossibility"-claims made by random people on the internet whose technical understanding is, well, that of random people on the internet.
 
Last edited by karmesin,
This device is definitely hackable. I’ve hacked all the others in the past yet don’t care, nor have the time to at this point. That & don’t want to get into trouble.
 
You are aware that NVIDIA uses ARM-based CPU architectures and that ARM CPU designs can be licensed and examined in extensive detail, right? These architectures have been thoroughly evaluated by numerous major companies, including those you trust with your most sensitive data.

Nevertheless, numerous ARM-based devices have been successfully reverse-engineered and compromised (even on hardware level). Just because certain parts of a system have been publicly leaked does not make it unhackable. If anything, access to such information can make it easier to identify and exploit potential vulnerabilities, even if some people claim that the code is flawless and completely secure. Just because you can identify wrong behaviour in non leaked sources much easier and find an entrypoint somewhere else.

But there is little point in arguing about this here anyway. Some people have seemingly internalized the Roman phrase "Carthago delenda est" to such an extent that they endlessly repeat "It will never be hacked" like some sort of religious mantra, apparently believing they are contributing something valuable to the discussion. They do not even seem to realize how incredibly annoying this constant repetition has become and ignore all facts around them like good internet trolls. At this point, discussing the subject with them feels a lot like arguing with a flat-earther.

What we know so far is that there are multiple entry points, data extraction is possible, and dumps already exist. Furthermore, several individuals with technical expertise far beyond my own have indicated that there are some promising approaches worth investigating. On top of that, we now have AI systems capable of identifying security vulnerabilities at an unprecedented scale, almost like finding candy on Easter. At the same time, we are dealing with a console that offers relatively little incentive for researchers to publicly disclose their findings.

For these reasons, I believe we should limit discussions to publicly available information and actual releases. We should avoid sharing internal details or creating false expectations, but we should also stop endlessly repeating "impossibility"-claims made by random people on the internet whose technical understanding is, well, that of random people on the internet.
i think you ignored what was said, the encryption scheme won't ever be hacked, it literally cannot be. the chance of you randomly guessing the private key is pretty much zero.

(the encryption scheme of the BCT / RCM port, which is what the signature and encryption key for said signature is for protecting.)

bypass is the only means possible, you are the flat earther in this context.
 
You are aware that NVIDIA uses ARM-based CPU architectures and that ARM CPU designs can be licensed and examined in extensive detail, right? These architectures have been thoroughly evaluated by numerous major companies, including those you trust with your most sensitive data.

Nevertheless, numerous ARM-based devices have been successfully reverse-engineered and compromised (even on hardware level). Just because certain parts of a system have been publicly leaked does not make it unhackable. If anything, access to such information can make it easier to identify and exploit potential vulnerabilities, even if some people claim that the code is flawless and completely secure. Just because you can identify wrong behaviour in non leaked sources much easier and find an entrypoint somewhere else.

But there is little point in arguing about this here anyway. Some people have seemingly internalized the Roman phrase "Carthago delenda est" to such an extent that they endlessly repeat "It will never be hacked" like some sort of religious mantra, apparently believing they are contributing something valuable to the discussion. They do not even seem to realize how incredibly annoying this constant repetition has become and ignore all facts around them like good internet trolls. At this point, discussing the subject with them feels a lot like arguing with a flat-earther.

What we know so far is that there are multiple entry points, data extraction is possible, and dumps already exist. Furthermore, several individuals with technical expertise far beyond my own have indicated that there are some promising approaches worth investigating. On top of that, we now have AI systems capable of identifying security vulnerabilities at an unprecedented scale, almost like finding candy on Easter. At the same time, we are dealing with a console that offers relatively little incentive for researchers to publicly disclose their findings.

For these reasons, I believe we should limit discussions to publicly available information and actual releases. We should avoid sharing internal details or creating false expectations, but we should also stop endlessly repeating "impossibility"-claims made by random people on the internet whose technical understanding is, well, that of random people on the internet.
The whole first part of this post sounds like you vastly misunderstood what bth said, ngl
 

Site & Scene News

New Hot Discussed User Submitted