Hacking Atmosphere 0.8 released 6.2.0 working

  • Thread starter Thread starter borngborn
  • Start date Start date
  • Views Views 56,598
  • Replies Replies 179
  • Likes Likes 16
Vanilla atmosphere doesn't support pirated nsps

These patches may or may not work with 6.2 https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/

I wonder if they've properly pwned TSEC or if it's just dumping the keys.

It looks like the exploit that mathileu described.

https://github.com/Atmosphere-NX/Atmosphere/commit/ed3770691519f025b5e7ebe353afa0fd3b224fd6

I'm not convinced it's possible to actually hack TSEC any other way, so it will be interesting how Nintendo will block it and whether 6.2 is going to turn out to be the highest we will ever be able to run.
 
Last edited by smf,
Error. I have placed all files in root SD and booted fusee primary bin payload. Goes through the black atmosphere welcome and set up, then nintendo logo, then switch logo, then this.

Please help
 

Attachments

  • IMG_20181129_192217.jpg
    IMG_20181129_192217.jpg
    1.9 MB · Views: 695
I wonder if they've properly pwned TSEC or if it's just dumping the keys.

Will be interesting to see Nintendo's stability response to this either way.

I can answer this, since I fully understand how this sploit works (and wrote it independently myself).

They did not pwn TSEC at all. What the sploit does is fool TSEC into thinking it's running with sole full control of the system (it thinks the CPUs / DMA are halted). Only then will it continue to generate the keys and decrypt the package1. To fool the TSEC, it needs to read the same constant values from MMIO memory space. This can be done by remapping the address space into DRAM by using SMMU translation. If a single bit from this space is different (like say the BPMP CPU is still running, the IO space would reflect that) then the TSEC would detect it. But by mimicing the same values in DRAM, the TSEC is fooled and continues decrypting package1.

To actually pwn TSEC you need to get code execution in the authenticated mode of the TSEC, which can then be used to reveal TSEC secrets. To date, nobody (and I'm pretty sure not even reswitched or switchbrew) has managed to do this.
 
Error. I have placed all files in root SD and booted fusee primary bin payload. Goes through the black atmosphere welcome and set up, then nintendo logo, then switch logo, then this.

Please help
That's a very pretty picture, good resolution, the text looks great. Perhaps it's that the error reporting code uses good anti-aliasing, or perhaps it is the camera, no idea.
 
Well I hope they release version 3.0 including gui changes along with 6.2 compatibility. Maybe they'll even throw in NSP install to hdd. fingers crossed.
 
I can answer this, since I fully understand how this sploit works (and wrote it independently myself).

They did not pwn TSEC at all. What the sploit does is fool TSEC into thinking it's running with sole full control of the system (it thinks the CPUs / DMA are halted). Only then will it continue to generate the keys and decrypt the package1. To fool the TSEC, it needs to read the same constant values from MMIO memory space. This can be done by remapping the address space into DRAM by using SMMU translation. If a single bit from this space is different (like say the BPMP CPU is still running, the IO space would reflect that) then the TSEC would detect it. But by mimicing the same values in DRAM, the TSEC is fooled and continues decrypting package1.

To actually pwn TSEC you need to get code execution in the authenticated mode of the TSEC, which can then be used to reveal TSEC secrets. To date, nobody (and I'm pretty sure not even reswitched or switchbrew) has managed to do this.
Can nintendo with an update change how this is handled so the TSEC wont give the keys?
 
Can nintendo with an update change how this is handled so the TSEC wont give the keys?

Yes they can. Mimicing MMIO with exactly the same behavior from a CPU is not trivial. What the TSEC now checks is mostly static data. If they change the TSEC to start to check for dynamic behavior of MMIO memory, well let's say it may not be possible to bypass it. There are also probably more than just one way to detect this hack.
 
Last edited by ,

Site & Scene News

Popular threads in this forum