Hacking Edit: It is safe to update to 6.2 using atmosphere

[proffk]

I guess we are in for a wait untill another exploit is found or keys get cracked.

 

[Daniel Navarro]

Let me be the first one who starts the "is it safe to update" threads by saying, that it's not safe right now.
As we all know (or should know) 6.2.0 update just got released and it changes how the keys are generated. What does this mean for the end-user? That no CFW currently works on 6.2.0.
https://mobile.twitter.com/hexkyz/status/1064692685569581056
View attachment 149801

6.2.0 confusion explained

Is it still possible to do NAND backup at least? I'm at 6.2 and use SX OS with CFW (No emuNAND)

 

[Kubas_inko]

Is it still possible to do NAND backup at least? I'm at 6.2 and use SX OS with CFW (No emuNAND)

You can always do a NAND backup.
And if you are on 6.2.0, how are you using SX OS?

 

[Daniel Navarro]

You can always do a NAND backup.
And if you are on 6.2.0, how are you using SX OS?

Well, I havent gone back SX OS since the update, so I dont know for sure if trying to use the dongle will break my switch or not. Thats why Im asking

 

[Kubas_inko]

Well, I havent gone back SX OS since the update, so I dont know for sure if trying to use the dongle will break my switch or not. Thats why Im asking

It won't break your Switch, you just won't be able to boot to 6.2.0 CFW

 

[Daniel Navarro]

It won't break your Switch, you just won't be able to boot to 6.2.0 CFW

So I can access to the SX OS menu and do the NAND Backup from there without issues? Thats a relief for the moment.

 

[Kubas_inko]

So I can access to the SX OS menu and do the NAND Backup from there without issues? Thats a relief for the moment.

yes

 

[Pluupy]

How is a bad thing that they’re not bricking the system

I don't understand what you're saying...

 

[Bakugo]

Remember when these same people said 5.0+ was unhackable right before the RCM exploit was released?

Why do you trust them?

 

[Kubas_inko]

Remember when these same people said 5.0+ was unhackable right before the RCM exploit was released?

Why do you trust them?

Because the same people (I am picking sciresm, who knew about RCM exploit) never said that (or if he did, he did not wanted to show he knows about working exploit).

 

[Bakugo]

(or if he did, he did not wanted to show he knows about working exploit).

Exactly, they're not trustworthy, they lie. "it's unhackable" today becomes "anyone can hack it" tomorrow.

 

[Kubas_inko]

Exactly, they're not trustworthy, they lie. "it's unhackable" today becomes "anyone can hack it" tomorrow.

They lie, cause they want the exploits to stay unpatched for as long as possible. Would you rather tell everyone about your amazing exploit, which means that ninty would know and they can patch it or wait for as many switches to be affected by it so that more people can use it once it is released?
And nobody says that 6.2.0 is unhackable. Everything will eventually get hacked.

 

[Shadow_man7]

They lie, cause they want the exploits to stay unpatched for as long as possible. Would you rather tell everyone about your amazing exploit, which means that ninty would know and they can patch it or wait for as many switches to be affected by it so that more people can use it once it is released?
And nobody says that 6.2.0 is unhackable. Everything will eventually get hacked.

You are right and to be honest if we'll have to go to play cat 'n mouse play exploit -> patch -> exploit -> patch. It's not a good time to release any exploit, because we don't have even ONE game which needs 6.2 update. So it would be wise to release it after a more 6.2 games going to be released.

 

[Kubas_inko]

You are right and to be honest if we'll have to go to play cat 'n mouse play exploit -> patch -> exploit -> patch. It's not a good time to release any exploit, because we don't have even ONE game which needs 6.2 update. So it would be wise to release it after a more 6.2 games going to be released.

That's the problem with deja vu and jamais vu. They are waiting for Ninty to patch it, but ninty does not know about it. But if they release it, ninty would patch it and we would lose some parts of an exploit (which still work).

 

[ZachyCatGames]

I don't understand what you're saying...

The way you worded it made it sound like you were saying its bad that the update didn’t brick systems

“They're not bricking the console, though. That's the worst part. The console can still be used, but many of it features will become unavailable. The salt on the wound.”

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

That's the problem with deja vu and jamais vu. They are waiting for Ninty to patch it, but ninty does not know about it. But if they release it, ninty would patch it and we would lose some parts of an exploit (which still work).

Jamais Vu has been patched for ages, and was also released ages ago

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

You are right and to be honest if we'll have to go to play cat 'n mouse play exploit -> patch -> exploit -> patch. It's not a good time to release any exploit, because we don't have even ONE game which needs 6.2 update. So it would be wise to release it after a more 6.2 games going to be released.

The number of games that a firmware has, has absolutely no impact on when an exploit is released kek

 

[Ian095]

Where did you get the idea that you don't have to update to play higher firmware games? If the games require a higher fw that has new master keys, then this cannot be bypassed.

Exactly, and because we don't have 6.2 keys we can't actually bypass update. He is thinking about Tinfoil bypass but it's relying on master keys from required software and we simply don't have it for 6.2.

Kinda what I meant by them changing something that would make the game not work. So guessing what they've done will cause any game that requires 6.2 onwards to no longer work on older firmware? Guess I might have to wait longer to play Smash Bros then...

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

How do you bypass having to update? I couldn’t get Civ VI to work on 6.0.1 and ended up updating to 6.1.

Tinfoil can bypass it during the installation of an NSP and it just works... From what's been said above though sounds like games from probably Smash Bros onwards might not work this way...

 

[Pluupy]

The way you worded it made it sound like you were saying its bad that the update didn’t brick systems

“They're not bricking the console, though. That's the worst part. The console can still be used, but many of it features will become unavailable. The salt on the wound.”

Um no? I clearly state that they aren't bricking the system because what they are doing in terms of law is not a brick, with that being the most challenging aspect of the issue as it absolves them of any legal action from afflicted users.

 

[lolcatzuru]

so i have a question, how exactly does this affect future games and something like tinfoil? im aware (currently) tinfoil allows a FW bypass but would that be something affected by the key change?

 

[Ian095]

so i have a question, how exactly does this affect future games and something like tinfoil? im aware (currently) tinfoil allows a FW bypass but would that be something affected by the key change?

I have little knowledge about this but a master key is required so unless the master key is somehow obtained it is impossible. I wouldn't say 6.2 will be unhackable forever and the key will likely be cracked or something eventually there just isn't an estimated timescale so people as always are losing it.

 

[MasterJ360]

interesting so now the Switch may end up sharing the same dilemma as the ps4 scene, but its too early to confirm that