Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[hippy dave]

True (although I'd much prefer if Atmosphere stop pumping out these patches if they want to not be associated with piracy)

The atmosphere team are not the people who tend to put out the patches.

 

[Draxzelex]

The atmosphere team are not the people who tend to put out the patches.

Its usually rajkosto is it not? Thought he was dead until he updated biskeydump to work on firmware 7.0

 

[hippy dave]

Its usually rajkosto is it not? Thought he was dead until he updated biskeydump to work on firmware 7.0

Yeah usually.

 

[Lacius]

The encryption keys can't be copyrighted, but they are arguably covered by DMCA/EUCD/whatever the equivalent law is called in your country.

Those laws cover any method, including the one they used to derive the key in 6.2.0 or the one that they are going to use for 7.0

It doesn't matter what they do, if their method circumvents a copy protection system then it's illegal.

Atmosphere doesn't include patches that do that, so they may be able to argue their case in court. The homebrew argument didn't work on the DS flashcart court cases, because the cards also supported commercial games out of the box. They were also being sold, so there was a strong legal case for Nintendo.

So the answer "it's illegal" is a red herring. The answer may be that they incorrectly think it's illegal, or maybe they don't want to tell you the real reason. Maybe they just like pretending that they are outwitting the legal system like some robin hood story.

Please don't conflate running Atmosphere with circumventing copy protection. They're not the same thing, and you can't circumvent copy protection with Atmosphere alone. CFW is not illegal, although it does violate Nintendo's TOS and comes with all of the consequences of doing so.

The 7.0.0 key isn't being released because it's the intellectual property of Nintendo, and it's illegal to release that. CFW that derives the key from the Switch itself is not illegal, and the chainloader being released within the next few days/weeks will mastefully allow for CFW on 7.0.0 without releasing the key nor burning an exploit.

 

[smf]

Please don't conflate running Atmosphere with circumventing copy protection. They're not the same thing, and you can't circumvent copy protection with Atmosphere alone.

Jailbreaking consoles is illegal in the US. Just because you have to grab a file from somewhere else to run pirated content, won't necessarily help you in court.

It would be like providing most of the ingredients for making meth and telling people to buy some acetone from your friend.

Maybe you win, maybe you won't.

The 7.0.0 key isn't being released because it's the intellectual property of Nintendo, and it's illegal to release that.

It's a randomly generated number, which isn't copyrightable as it's too short and lacks any artistic input.

If it's illegal to distribute the key (like it's illegal to distribute other illegal numbers) then it's only because it's covered by DMCA anti circumvention, not copyright. This has all been tested in court quite extensively due to CSS/AACS/HDCP.

If you're right and it's not a DMCA issue, then it's no different to these keys https://en.wikipedia.org/wiki/Texas_Instruments_signing_key_controversy if the keys were copyrightable then TI wouldn't have backed down.

It does make an interesting game for them to play though.

 

[ZachyCatGames]

Its usually rajkosto is it not? Thought he was dead until he updated biskeydump to work on firmware 7.0

Well. Rajkosto isn't part of the ReSwitched team

 

[Draxzelex]

Well. Rajkosto isn't part of the ReSwitched team

But he's usually active on the ReSwitched server. Note: I am not saying rajkosto is a part of ReSwitched.

 

[ScarletDreamz]

Again, he's keeping the exploit private. Releasing the code for the new method won't give away how he got the keys.

I just wanted to see, if he keeps everything private, how much time would TX take to figure it out by themselves.

 

[ZachyCatGames]

I just wanted to see, if he keeps everything private, how much time would TX take to figure it out by themselves.

He’s keeping the keys needed to sign it private though . So they will probably need to figure it out on their own, unless they use SciresM’s key deriver thing directly from the atmosphere releases page without any modifications

 

[8BitWonder]

He’s keeping the keys needed to sign it private though . So they will probably need to figure it out on their own, unless they use SciresM’s key deriver thing directly from the atmosphere releases page without any modifications

I'm assuming they're just going to chain-load the "magic" payload as a work-a-round until they've dumped the keys themselves.

 

[ZachyCatGames]

I'm assuming they're just going to chain-load the "magic" payload as a work-a-round until they've dumped the keys themselves.

Probably ¯\_(ツ)_/¯

 

[Diablos90]

Hi guys, I have a question: can I set a custom boot logo when Atmosphere is launched through fusee-primary.bin?

When I launch Atmosphere through fusee-primary.bin I only see a black screen with logs (loading stage 2 and kips).
I searched on Google, but I only found this page.

According to that bug report, would be possible to set a custom boot logo editing the BCT.ini file to hide non-error logs at startup, but I didn't find any other info about this.
It's really possible to set a custom boot logo editing the BCT.ini?

Thanks in advance

 

[ZachyCatGames]

Hi guys, I have a question: can I set a custom boot logo when Atmosphere is launched through fusee-primary.bin?

When I launch Atmosphere through fusee-primary.bin I only see a black screen with logs (loading stage 2 and kips).
I searched on Google, but I only found this page.

According to that bug report, would be possible to set a custom boot logo editing the BCT.ini file to hide non-error logs at startup, but I didn't find any other info about this.
It's really possible to set a custom boot logo editing the BCT.ini?

Thanks in advance

The official splash screen not appearing on 6.2.0+ is a bug that has been fixed and will be included in the next update.

There isn't any way to official add a custom splash screen, but you can add one by downloading atmos source, replacing the splash in the source, and then compiling it

 

[8BitWonder]

There isn't any way to official add a custom splash screen, but you can add one by downloading atmos source, replacing the splash in the source, and then compiling it

You can add a custom splash to Atmosphere without compiling a custom build.

Just add:

[stage2]
custom_splash = <path to bmp>

to your BCT.ini

Here is the issue showing it.

 

[ZachyCatGames]

You can add a custom splash to Atmosphere without compiling a custom build.

Just add:

[stage2]
custom_splash = <path to bmp>

to your BCT.ini

Diablos90 linked the issue showing it.

Really? Neat !

 

[Diablos90]

The official splash screen not appearing on 6.2.0+ is a bug that has been fixed and will be included in the next update.

There isn't any way to official add a custom splash screen, but you can add one by downloading atmos source, replacing the splash in the source, and then compiling it

Oh, thanks for the clarification

I never used Atmosphere on lower firmwares, so I didn't know that actually it haves a boot logo

EDIT:

You can add a custom splash to Atmosphere without compiling a custom build.

Just add:

[stage2]
custom_splash = <path to bmp>

to your BCT.ini

Here is the issue showing it.

Awesome, I hoped it was possible

it's just the BCT.ini string I was looking for (with no luck until now).

Thank you

 

[LoneFlo]

You can add a custom splash to Atmosphere without compiling a custom build.

Just add:

[stage2]
custom_splash = <path to bmp>

to your BCT.ini

Here is the issue showing it.

I tried 8, 16, 24 and 32 bits and I always get "invalid image depth".

 

[8BitWonder]

I tried 8, 16, 24 and 32 bits and I always get "invalid image depth".

It needs to be a 32-bit bitmap and rotated 90 degrees counter-clockwise.
Follow the instructions here carefully, hopefully it works for you.
https://github.com/CTCaer/hekate/blob/master/README_BOOTLOGO.md

 

[LoneFlo]

It needs to be a 32-bit bitmap and rotated 90 degrees counter-clockwise.
Follow the instructions here carefully, hopefully it works for you.
https://github.com/CTCaer/hekate/blob/master/README_BOOTLOGO.md

Thank you for the link. The problem was I saved as BMP 32 bits XRGB, but it needed to be in ARGB. By default, Photoshop uses XRGB.

 

[LoneFlo]

My bmp file is good now, but atmosphere 0.8.3 won't display any splash screen though.