Incognito_RCM - wipe personal information to reduce risk of ban

LightBeam · Oct 5, 2019

Wtf are you talking about

tomi1578 · Oct 5, 2019

Txustra said:
How do I do to apply this to emummc instead of sysnand?

use the nro version on emummc

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

LightBeam said:
Same question, don't want to erase the prodinfo on the sysnand by accident

same answer use nro version on emummc

LightBeam · Oct 5, 2019

The point of this RCM release is to not use the nro made by blawar, so we can keep our vanilla/kosmos atmosphere and not use a sysmodule

Sonansune · Oct 5, 2019

hooray

Rahkeesh · Oct 5, 2019

Wiping prodinfo makes your *console* immune to ban because that's how Nintendo uniquely identifies consoles. If they decide they want to ban entire accounts that report invalid prodinfos and you set one up then your screwed, but so far they haven't been doing that. Safest bet would be to not have an account set up on or use a throwaway or kefir one on your incognito'd nand.

linuxares · Oct 5, 2019

Rahkeesh said:
Wiping prodinfo makes your *console* immune to ban because that's how Nintendo uniquely identifies consoles. If they decide they want to ban entire accounts that report invalid prodinfos and you set one up then your screwed, but so far they haven't been doing that. Safest bet would be to not have an account set up on or use a throwaway or kefir one on your incognito'd nand.

Again, no. It doesn't make your immune. Just probably less prone to get a ban. There is a TON of info that is collected. Atmosphere have their own way to block telemetry. But not all CFW have it and we never know what Nintendo can do next.

Rahkeesh · Oct 5, 2019

They can collect all they want, they still need a unique hardware identifier to ban unique hardware. If you're running two seperate nands they likely look very different in terms of what is installed and what programs are run, they will have their own separate logs, etc. They can look at stuff like your access point or IP but its very hard to distinguish between one system with two boots and two systems on the same network. They can look at joycon serials or gamecard certs but again those can move between systems. There aren't a variety of hardware configs that generate unique IDs like on PCs. I don't see how they are going to single out a piece of hardware without making guesses and false positives once you remove the very thing whose sole purpose is to single out a piece of hardware, and at that point you might as well ban a shared account or IP address.

linuxares · Oct 5, 2019

Rahkeesh said:
They can collect all they want, they still need a unique hardware identifier to ban unique hardware. If you're running two seperate nands they likely look very different in terms of what is installed and what programs are run, they will have their own separate logs, etc. They can look at stuff like your access point or IP but its very hard to distinguish between one system with two boots and two systems on the same network. They can look at joycon serials or gamecard certs but again those can move between systems. There aren't a variety of hardware configs that generate unique IDs like on PCs. I don't see how they are going to single out a piece of hardware without making guesses and false positives once you remove the very thing whose sole purpose is to single out a piece of hardware, and at that point you might as well ban a shared account or IP address.

And that's why Nintendo update the telemetry. 9.0.0+ added a whole heap of new identifiable options. https://switchbrew.org/wiki/Calibration

Godofcheese · Oct 5, 2019

Never used incognito in any form, only used dns.
How does this work when you have a Nintendo account linked?
Will that be removed?

Thanks

MYFW · Oct 5, 2019

It works witch Atmosphere Emunand on 9.0?

linuxares · Oct 5, 2019

Godofcheese said:
Never used incognito in any form, only used dns.
How does this work when you have a Nintendo account linked?
Will that be removed?

Thanks

It just seem to remove the serial number when I check the sourcecode. I might be wrong. I'm just reading inside keys.c

EDIT: Sorry it does some more.

Serial number, deletes client cert, deletes private key, deviceid 1 and 2, deletes device cert 1 and 2 and deletes the device key.

Something whatever · Oct 5, 2019

Oh so its like deleting Browsing history when you....umm yeah awesome

Engezerstorung · Oct 5, 2019

i thought that incognito was removing the infos that enabled the switch to be allowed to connect to nintendo? and that since its like that even if the switch send info there is no one to listen to them on the other side?

linuxares · Oct 5, 2019

Engezerstorung said:
i thought that incognito was removing the infos that enabled the switch to be allowed to connect to nintendo? and that since its like that even if the switch send info there is no one to listen to them on the other side?

In theory yes, and probably so forever. But we never know 100% what Nintendo do next. They might implement another SSL cert to do a handshake. To be 100% risk free from bans for hacking, it's to have another untouched switch. Incognito it does reduce the chance to get a ban for sure.

Engezerstorung · Oct 5, 2019

linuxares said:
In theory yes, and probably so forever. But we never know 100% what Nintendo do next. They might implement another SSL cert to do a handshake. To be 100% risk free from bans for hacking, it's to have another untouched switch. Incognito it does reduce the chance to get a ban for sure.

well, that's why we usually for greenlight before updating isn't it? and in this specific exemple case we coul remove this certificate to get back to square 1, no?

linuxares · Oct 5, 2019

Engezerstorung said:
well, that's why we usually for greenlight before updating isn't it? and in this specific exemple case we coul remove this certificate to get back to square 1, no?

Possibily. As I say, there is never a 100% sure way. It's the risk you take.

Dr.Hacknik · Oct 5, 2019

shchmue said:
i'm surprised you wanted to get a proof of concept out without full precautions in place, that's irresponsible

yeah you can't at the moment do a streaming hash, we only just figured that out, but there's no RAM limitation that could keep you from just allocating a 4MiB buffer and reading the whole prodinfo in at once then hashing it in one go. and if you bench it you'll be shocked, even an asm implementation tailored to armv4t from openssl will take 10-100x + longer than se

Lol I think you're missing the point, it's a WIP. Experimental if anything. With proper disclaimers that it's early work is fine, it's on the user for using an experimental solution.

huma_dawii · Oct 5, 2019

linuxares said:
I love it when homebrew devs help each other

I know, imagine what the community could accomplish if they got together... But no, they rather fight and get nothing done and block each other progress....

Annoying.

KuranKu · Oct 5, 2019

i would like to add one thing.
ability to add google accout or what ever to backup the file there for user convenience and prodinfo security , as an possible option

correction: a companion app or something

BulletExodus · Oct 5, 2019

Very nice.

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

The inadequate, autocratic beast!

Well-Known Member

The inadequate, autocratic beast!

Insane

Well-Known Member

The inadequate, autocratic beast!

Gazer of the East

Well-Known Member

The inadequate, autocratic beast!

Well-Known Member

The inadequate, autocratic beast!

Ashley | Developer | Trans

Well-Known Member

I am KranK

Member

Similar threads

Popular threads in this forum