banning means you get banned from dauth, which prevents you from obtaining edgetokens, which are required to download games, updates, dlc and access eshop.
it does not ban you from accessing atum, which is what provides you firmware updates...
turns out the sysmodules just used sfdnsres ipc commands not implemented into atmosphere (that were new in 23.0.0), and that some others used the old ones, dns.mitm worked for the ones who used the old ones, and not the new ones.
atmosphere...
the serial number was always a cosmetic thing, the real effect is the ssl certificate being blanked.
it's your certificate they block from AWS/dauth, not your serial number.
anyway it turns out the issue for dns.mitm was just that some, not all...
next version of atmosphere fixes that, dns.mitm wasn't filtering all the dns requests in 23.0.0
anyway damage already done, you done sent telemetry to nintendo and updated eveyrthing that was in your emummc
from what can be seen they changed the dns handler from easycurl/libcurl to c-ares
speculative:
host file ignored unless browser ...?
(if yes, dns.mitm has become obsolete - rip - would require rework of its current existence, or alternatively...
no https communication established -> no traffic between their servers
no client certificate to use -> no ssl/https communication possible.
Yes, that's the core concept. Currently dns.mitm doesn't work (supposedly), which means ctest is the only...
"the browser" -> no such thing as an official browser provided by Nintendo or atmosphere.
theres a probability whatever homebrew you're referencing respects the hosts file (placebo), and doesn't actually query through sfdnsres (...
I'm assuming this is fetching the backup file(s) atmosphere makes automatically on the sd card, not that there are many legitimate reasons for a homebrew to touch your console unique certificate.
the intent with blanking your console unique ssl...
We was at the "we are doomed" point right now, we only "stole back" 9MB in 23.0.0 by trimming down reserved memory pool 3 official applets use by using convoluted patches.
or well, the only people doomed are the ones who insist on running...
I wasn't sure if anything had changed, and didn't want to continue compiling stuff with the old libnx if it wasn't compatible, my bad. I use the docker container from the hub, devkitpro/devkita64 with a minimal compose.
Thanks btw for...
What for?
the 7 month outdated https://hub.docker.com/r/devkitpro/devkita64 or libnx? (libnx releases are a switchbrew concept anyway, not DKP)
because you can just compile libnx and run a make install yourself...