There's a 90DNS Tester that you can run from your Switch to check if DNS MITM is actually working. Good to know that 90DNS has it's own script as well, thanks for mentioning that.
There's also this fix. I haven't tested it personally since I'm using Exosphere and DNS MITM. As for 90DNS, it requires that you manually set it up for every wireless connection. There's 90DNS setter as well, but I haven't tried it out yet.
Only thing they are currently missing in their hekate_ipl.ini file is the kip1patch=nosigchk line in both CFW configurations. Without them I believe that sigpatches won't work when chainloading fusee. (Provided I'm reading it correctly through sys-patch, which says Patched instead of Patched for fs patches, i.e. sys-patch did the patching instead of sigpatches.)
I've read it couple of times already but I couldn't find any info about this? Can you show me the source? Too bad if it's true, DBI really is an amazing tool.
It doesn't hurt to have exosphere's prodinfo blanking enabled while also having 90DSN/DNS MITM in place. Ever since 17.0.0 firmware got released and they fixed the prodinfo blanking, resulting in an error in both OFW and Atmosphere. Therefore, to me at least, it serves as a warning of sorts that maybe, just maybe, DNS MITM / 90DNS stopped working properly and my console tried to connect to the Nintendo servers, resulting in Atmosphere crashing with a specific error (can't remember which one right now, I'll have to look it up later).
@impeeza wrote a detailed explanation when I asked him the similar question. You can check his reply here.
I do not even remember that post, Thanks a lot, recently someone asked on other post and I has to write almost everything again.
Thanks, that was very helpful. The 90dns-tester shows that all domains are blocked (DNS-MITM only atm). I also added the fix to my atmosphere/exefs_patches directory.
duckbill has stated multiple times that dbi has been discontinued and he's moved onto other projects already. This post is the earliest instance of him saying as such. Personally, I don't really mind its absence but we are in a very bad situation where no title installers are being actively updated. If a future firmware update breaks all currently existing ones, we're in trouble.
If 90DNS and dns.mitm can function on their own but not exosphere/Incognito, then the issue lies in the former. Not to mention that you do not obtain extra protection. There are ways Nintendo can obtain info through both being active at the same time. They are theoretical which means you're paranoid about a scenario that has no precedent and if you're that paranoid, then you would also realize the double protection is meaningless. This is similar to people who have both the patches on their SD card as well as sys-patch; its extra space taken on your SD card for no additional payoff. I'm not going to police what you or other people put on your SD card but I'm not going to tell people to waste room on their cards without a good reason.
Even DBI can tell you real Serial number even if you have BOOT0 edited with Incognito RCM and Atmosphère's blank_prodinfo
Ah, I do remember seeing his posts about discontinuing DBI, but as far as I know rashevskyv picked it up? Unless he dropped it as well? Or is there something else that I should be aware of?
So, what you suggest is to use either 90DNS or DNS MITM, and not prodinfo blanking? I do know that having both sys-patch and sigpatches at the same time hardly serves a point.
Ouch. So prodinfo blanking is pretty much meaningless?
Fair enough, I do like to keep my SD card as clean as possible so I'll reword my suggestions in the future replies (and clean up mine as well by doing that). It really helps to hear criticism from time to time as I'm hardly an expert, but I'd like to do my part and help others if possible, purely based on my own experience.
somehow seems you are correct, I wondered how DBI was able to give my original serial even I have my EmuNAND incognito and blank prodinfo on atmosphère, asked and the answer was "creative coding" but if DBI was able I guess big N will be able too.
Nah its just him hosting the .NRO file since duckbill presumably closed the GitHub page for the original repo. And since its closed source meaning no open source code to work with, I doubt that other person is actively developing it. He even specifically mentions the author is duckbill and not himself.
If you want something to keep you safe while using FTP, the homebrew store, or pseudo-online LAN play, then yes. If you aren't using any of these utilities, don't even bother with 90DNS or dns.mitm. My emuMMC is allergic to Wi-Fi settings.
I'm not surprised. After all, SciresM himself stated that the protection it provided wasn't fullproof. There is information that Nintendo can still obtain without PRODINFO such as the battery serial, which may or may not be linked. I'm pretty sure the only reason he created exosphere was so that people would stop blanking their PRODINFO because without a backup, you've basically banned yourself. And this has happened multiple times if you search up people losing their PRODINFO backups. For this reason, I have never ever recommended Incognito and by extension exosphere.
No seriously, as a fellow tech supporter, your contribution is greatly appreciated. Nowadays, I only intervene when malicious misinformation is being spread. Your advice is basically on point most of the time so keep up the great work. I'm more nitpicky because I hate how the community turned its back on tools like 90DNS or why the reentry guide makes users chainload fusee through Hekate.
Ah, I thought it was just him acknowledging the previous author. Well, I guess the situation is pretty... gray at the moment.
Understood.
I see. I remember reading about prodinfo protection in exosphere's template, I think. But seeing that DBI correctly guessed mine, I can expect the same coming from Nintendo. People losing their prodinfo backups (and any backups in general) is, sadly, too much of a common thing, indeed.
Thank you very much! Thanks to you, impeeza and binkinator (while he was still active), I've solved pretty much all of the problems I've encountered so far (not that I'm actively looking for new ones, that is ^^). And I've learned a thing or two along the way from other users as well. Hayato213. Dust2dust and BigOnYa lurk around here a lot and their replies helped me here and there.
As soon as you mentioned it, I checked mine as well and "creative coding" did the job properly.
That has ben answered several times, there are two class:
And when EMUtool has target card options all grayed out?
Emutool BACKUP AND RESTORE the EmuNAND
Since you're probably new to the Switch hacking scene, I'd suggest that you go through these two guides: NH Switch guide and Rentry.org Switch guide. Getting familiar with the terms used will make updating your Switch and troubleshooting your issues much easier for you.Hi all,
I'm new to all of this, somewhat a noob, and I'm kinda stuck in the process.
I have an unpatched v1 Switch with a 128gb microSD in it: I have the rcm-clip and the device has hekate on it.
I have the tegrarcmgui installed on the pc. And i've downloaded some nsp, nsz and xci files on my computer. I also did the 90DNS where you block the Nintendo-server (or so?),
And this is where i get stuck
I want to put the games on the Switch so I can play some Switch-games.
What do I need to do from this point on? I feel like being far away, and close at the same time
bootloader/hekate_ipl.ini file, therefore booting into Hekate, followed by Launch and selecting either emuMMC or sysMMC CFW, depending on which one you use, will result with the sigpatches working properly again).
@
Xdqwerty:
