Incognito_RCM - wipe personal information to reduce risk of ban

linuxares · Oct 5, 2019

KuranKu said:
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

It can be hard to accomplish from RCM mode I reccon. I wonder if the network card is even active at that stage... hmm?

KuranKu · Oct 6, 2019

linuxares said:
It can be hard to accomplish from RCM mode I reccon. I wonder if the network card is even active at that stage... hmm?

yeah so maybe a background module or companion app idk , my point is to be as safe as posible for ppl that play with prodinfo

tomi1578 · Oct 6, 2019

LightBeam said:
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

so go complain to scriesm and tell him to allow the nro
and keep your emummc un incognitoed

Localhorst86 · Oct 6, 2019

tomi1578 said:
so go complain to scriesm and tell him to allow the nro
and keep your emummc un incognitoed

Having PRODINFO write protected by default is a safety feature to prevent malicious apps (e.g. brickachu) from messing it up intentionally. At least no one is actively blocking you from using a kip module to disable the write protection.

Deleted member 442567 · Oct 6, 2019

jimzrt said:
Incognito_RCM

since Incognito by blawar doesn't work on vanilla atmosphere, I made a payload to use with hekate (or any other payload injector) with the same functionality.
Incognito_RCM wipes personal information from your Nintendo Switch by removing it from prodinfo.

Functionality:

wipe personal information on sysnand/emunand

backup prodinfo from sysnand/emunand

restore prodinfo to sysnand/emunand

Since NAND memory is encrypted, this is based on shchmue's Lockpick_RCM to first get the neccessary encryption keys.
You can apply Incognito_RCM directly after installing atmosphere or any time after and it has the advantage that you don't need to set 90DNS after an internet connection and possibly communication with nintendo servers is already established. (You can apply 90DNS anyway)

This has only been tested by me on firmware 8.1.0, so please test it and report back.
Since it has only been tested by me, keep a hekate nand backup ready to be safe.

source: https://github.com/jimzrt/Incognito_RCM
releases: https://github.com/jimzrt/Incognito_RCM/releases

Disclaimer:
This is early stage and there is no guarantee that everything works as expected! Please have a hekate NAND backup ready!

Changelog:

v0.1.0

much faster read and write speed (not sector by sector anymore)

much more validation and verification (still not perfect)

more error handling (still not perfect)

backups aren't overwritten, old backups are renamed

check for backup before applying incognito

auto-restore backup if something goes wrong

as always, have a NAND backup ready!

v0.0.2

Removed external libraries and better handling of reading big chunks of memory.

Does this work for SX OS Users too?

BlastedGuy9905 · Oct 6, 2019

Hayato213 said:
I like it, atleast people now doesn't have to deal with Blawar's malware.

haha blaware haha

LightBeam · Oct 6, 2019

tomi1578 said:
so go complain to scriesm and tell him to allow the nro
and keep your emummc un incognitoed

Already used the sysmodule a while ago, I was just explaining to you the purpose of this release
But it seems you're only here to behave like a jerk, I take this opportunity to let you know that everyone would do without your childish rudeness, I now dare to take the risk of trusting your intelligence and hope you won't go any further.

hippy dave · Oct 6, 2019

RetroDarioGaming said:
Does this work for SX OS Users too?

It would work on sysnand regardless of cfw. For partition-based emunand, it'd probably work if you make a correctly-configured emummc/emummc.ini (I don't know the right configuration for sx emunand, but someone can probably tell you), for file-based it might not work as-is.

jimzrt · Oct 7, 2019

New release:
https://github.com/jimzrt/Incognito_RCM/releases/tag/v0.2.0

more validation
code cleanup and refactoring

And a few screenshots:

I tested everything pretty meticulously on my own device and haven't had any hiccups yet.
But I am still missing real test reports! Would be glad for some of you to try it and report back.

Adran_Marit · Oct 7, 2019

jimzrt said:
New release:
https://github.com/jimzrt/Incognito_RCM/releases/tag/v0.2.0

more validation

code cleanup and refactoring

And a few screenshots:

I tested everything pretty meticulously on my own device and haven't had any hiccups yet.
But I am still missing real test reports! Would be glad for some of you to try it and report back.

@linuxares huh prodinfo hashing.....

linuxares · Oct 7, 2019

Adran_Marit said:
@linuxares huh prodinfo hashing.....

Yes, we known about that one since forever

Still not enough to get a donor nand working :/

Adran_Marit · Oct 7, 2019

linuxares said:
Yes, we known about that one since forever Still not enough to get a donor nand working :/

ah darn... wish my console was working so I could test stuff

SaulFemm · Oct 7, 2019

Crusatyr said:
Not to be that asshole, but Incognito is open source. Maybe next time you can actually put forth the effort to know what you're talking about before letting your ignorance show?

My mistake entirely. I assumed it was closed-source based on some of his previous projects as well as the tirade he went on against open-sourcing his code.

Adran_Marit · Oct 7, 2019

SaulFemm said:
My mistake entirely. I assumed it was closed-source based on some of his previous projects as well as the tirade he went on against open-sourcing his code.

life pro tip: Never assume, you make an as out of you and me

wiewiec · Oct 7, 2019

If I never used cfw on nand only emunand am I ok or I must apply it to nand also?

jimzrt · Oct 7, 2019

wiewiec said:
If I never used cfw on nand only emunand am I ok or I must apply it to nand also?

Only emunand is then required.
Sysnand is for those who installed cfw on sysnand.

feral · Oct 7, 2019

@jimzrt this seemed to work fine on my 9.0.1 emunand. I was able to make a backup of prodinfo and Atmosphere reports a blank console serial, just like when I previously applied icognito to my 8.1.0 emunand. I didn't test the restore feature.

metaljay · Oct 7, 2019

jimzrt said:
New release:
https://github.com/jimzrt/Incognito_RCM/releases/tag/v0.2.0

more validation

code cleanup and refactoring

And a few screenshots:

I tested everything pretty meticulously on my own device and haven't had any hiccups yet.
But I am still missing real test reports! Would be glad for some of you to try it and report back.

This is looking excellent! Any chance you can get it bundled with the home-brew App Store?

jimzrt · Oct 7, 2019

feral said:
@jimzrt this seemed to work fine on my 9.0.1 emunand. I was able to make a backup of prodinfo and Atmosphere reports a blank console serial, just like when I previously applied icognito to my 8.1.0 emunand. I didn't test the restore feature.

thank you for testing!

metaljay said:
This is looking excellent! Any chance you can get it bundled with the home-brew App Store?

Thanks, will surely apply for adding this to the homebrew app store, but first want to get some testing!
@feral 's report is the only one so far...

ZachyCatGames · Oct 7, 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.

But here’s the thing, there is still hardware unique identifiable information. It doesn’t nuke everything from prodinfo, and there also some console unique stuff in fuses.

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

That stuff is only included in the PRODINFOs for systems manufactured using firmware >=9.0.0. None of that new stuff will be on any of our consoles.

The inadequate, autocratic beast!

I am KranK

Well-Known Member

Robert'); DROP TABLE members;--

Well-Known Member

where's the updated autopsy report

Well-Known Member

BBMB

Active Member

Walküre's Hacker

The inadequate, autocratic beast!

Walküre's Hacker

Well-Known Member

Walküre's Hacker

Well-Known Member

Active Member

Active Member

Well-Known Member

Active Member

Well-Known Member

Similar threads

Popular threads in this forum