With a background process that could scan everything running in memory while idle on the homemenu, they could identify Luma patches that shouldn't be there, and prevent any software from launching. And as far as un-A9LHaxing the console, I'm surprised Nintendo doesn't patch it yet and remove A9LH. If hackers can place files on a system, Nintendo can too. There's no reason that official signed software with full kernel and ARM9+ARM11 access can't undo A9LHax, I'd have to call bullshit. I think they're just stuck on how to implement the fix across all 3DS variants without bricking everyone's consoles.
With a background process that could scan everything running in memory while idle on the homemenu, they could identify Luma patches that shouldn't be there, and prevent any software from launching.
And with putting a scan in memory (which will be pretty noticeable due to the resource intensive nature of the task you're suggesting - as it will have to look in-depth for each item in memory, to prevent spoofs of "rogue" items) we can also just find that patch, and either NOP it completely so it doesn't run, or spoof the results by injecting our own code into the process to tell it "yup. We're all good!" whilst Luma patches are sitting right next to it in memory.
And as far as un-A9LHaxing the console, I'm surprised Nintendo doesn't patch it yet and remove A9LH. If hackers can place files on a system, Nintendo can too. There's no reason that official signed software with full kernel and ARM9+ARM11 access can't undo A9LHax, I'd have to call bullshit. I think they're just stuck on how to implement the fix across all 3DS variants without bricking everyone's consoles.
Nope, it's definitely not as easy as you make out [to remove A9LH].
If hackers can place files on a system, Nintendo can too. There's no reason that official signed software with full kernel and ARM9+ARM11 access can't undo A9LHax, I'd have to call bullshit.
You're forgetting A9LH hooks the system
BEFORE Nintendo's software runs. We have full control, and thus can stop or start things we want even before launching the FW. We throw the first punch as it were.
Think of A9LH like a PC's Bios. The Bios is completely separate from the OS and merely "hands over" control once it does it's POST check etc (simplified of course, but that's the general idea).
If you have Malware in your BIOs (entirely possible. There was a recent Mac virus which did this) - reinstalling the OS will do
NOTHING because it's in the Bios; The section of firmware which hands over to your OS. The only method to remove such malware is to completely replace the Bios chip, as flashing does not guarantee the malware will not store itself in a Bios backup (which every motherboard does in case of a bad Bios update) and re-install itself.
Same for A9LH. Nintendo cannot force A9LH out of a system because A9LH effectively resides in the 3DS' Bios. Short of removing the chip completely, you can't "shoo" it away like you can Homebrew. You can call bullshit all you like, but this is definitely
NOT as simple as "patch a few things and away we go!". There was a reason some referred to A9LH as the "god exploit"[because we have full control before Nintendo's FW loads up. We can get in early, NOP any checks/attempts to use A9LH and carry on].
I think they're just stuck on how to implement the fix across all 3DS variants without bricking everyone's consoles.
Wrong. They're not doing it because of the above. They also tried sorting this mess out before, by changing how the N3DS does it's whole "crypto" thing with the kernel and that worked out....not (hey, while we release a new 3DS version with improvements, why not make it harder to crack...which didn't quite work to plan in the end..).
Our old friend Yifan Lu did a really good blog post on this before actually (find it
here) but in short this was Nintendo's
original crypto system to help prevent Homebrew/A9LH used in the O3Ds and here's t
he N3DS implementation. They tried (obviously. There's loads more activity going on in the N3DS diagram Vs the old one) but evidently failed. The funny thing is, Nintendo's "new and improved" crypto/Bootloader system is
WHY A9LH is so successful (the wonderful irony).
tl;dr for those with short attention spans:
They can't remove A9LH because we get the first "hit" in early during boot. If Nintendo got in before us, then it's possible they could remove A9LH in some form but they can't because they're more a less last to boot in the boot chain. They can't change that either, short of somehow remaking how the 3DS does it's boot sequence, and even then that won't be possible in update form (it would, however, be flashed onto newer 3DS' off the production line) so existing A9LH installs will be forever safe unless the user screws up and only then will it be removed from the system (but by the user's own fault, not through Nintendo removing it).