TuxSH is like the darkcoder. He just codes from the Shadows.TuxSH is also putting in a lot of work. After all, he co-developed Luma for the 3DS.
TuxSH is like the darkcoder. He just codes from the Shadows.TuxSH is also putting in a lot of work. After all, he co-developed Luma for the 3DS.
So because it wasn't released on a date that was never confirmed this is cause for you to believe the CFW is never coming?
What about the commits to the GitHub by SciresM or the discussions taking place in the reswitched Discord?
If you have no evidence other than theories and crazy speculation then it's probably best you don't share. It has been proven MULTIPLE times that Atmosphere is still being worked on. SciresM has commented in the Atmosphere thread MULTIPLE times stating that it is not dead. It has been shown MULTIPLE times that the so called release date was never confirmed as a release date, it was a disclosure window created by Ktemkin as the developer who found the exploit, this was decided upon to give Nintendo and other Manufacturers who used the vulnerable SOC/Chipset adequate time to do something about it. RCM was only discovered because it was leaked by someone.
He's done very little compared to the other project members, even calling his fusee launcher a contribution is almost unreasonable given how little effort it takes to implement. Why do you need to know about him?Hi I would like to know if Ktemkin is still working on Atmosphere?
Mate I'm still working on sybian based emu that's never been released and a custom madOS for my old 33XX lol commenting means nothing and yes that seems to be the only team actually doing anything but bicker lolBut you stated it would never come out....
Are you still standing by that statement even though you have been given proof it is still being worked on?
Kate did not find the flaw, F0F (shuffle) was the one who disclosed it.cause i just wanted to know if she was or not since she discovered the tegra flaw.
I'm sure you have at least found another exploitable bootROM vulnerability and implemented it, yes? Other than, of course, writing a Tegra SDMMC driver.He's done very little compared to the other project members, even calling his fusee launcher a contribution is almost unreasonable given how little effort it takes to implement. Why do you need to know about him?
https://www.nvidia.com/en-us/product-security/ -> Acknowledgments. The flaw was found and implemented independently: I somehow get the feeling nvidia is a trustable source.Kate did not find the flaw, F0F (shuffle) was the one who disclosed it.
Writing a python script that takes advantage of an exploit is not the same as discovering an exploit. By the way, where's your implementations of said software? Nice fallacy.I'm sure you have at least found another exploitable bootROM vulnerability and implemented it, yes? Other than, of course, writing a Tegra SDMMC driver.
This was published before that http://misc.ktemkin.com/fusee_gelee_nvidia.pdfAnyhow, to steer this thread back on its track: if you could take the time to read fail0verflow's blog (blog/2018/shofel2/) you could make up from it that it was F0F who found the exploit first, right?
Somewhat irrelevant given the first "public" release of real information on the exploit was thrown onto a freakin' pastebin. Damn, that's a dude we should be cheering for. Imagine where we'd be without that kind soul.This was published before that http://misc.ktemkin.com/fusee_gelee_nvidia.pdf