So, a post on twitter was made by (I think plutoo?) that says "NO" to a question about heaphax. Is heaphax dead?
How ironic to see you on one post I commented on, then another.AFAIK yup. I think they patched the exploit in 11.0
Not exactly an arm11 kernel exploit, but a (n3DS only) way to take over a service called NS to get the am:u service (legit CIA installation and formerly downgrading).What even is heaphax
Fuck so it is dead?Not exactly an arm11 kernel exploit, but a (n3DS only) way to take over a service called NS to get the am:u service (legit CIA installation and formerly downgrading).
Tbh I myself couldn't tell you how it was patched, but smea himself said:Fuck so it is dead?
I don't know how, though. Maybe I'll look around 3dbrew later, but it's really a pain in the ass to navigate the vulnerabilities/exploits page.it was mostly fixed in 11.0; don't think it can be used to takeover ns anymore. so that's that.
Yeah because legit cia installation would be a big step up for 11.0Tbh I myself couldn't tell you how it was patched, but smea himself said:
I don't know how, though. Maybe I'll look around 3dbrew later, but it's really a pain in the ass to navigate the vulnerabilities/exploits page.
Uh, no. That's memchunkhax2.1, a full blown arm11 kernel exploit. This isn't that, it's a service takeover to get legit CIA installation without kernel access.I mean, from what I read heaphax isn't dead or patched. Its still there but Nintendo added a security to memchunkhdr to not be able to write on it. Making it harder to use the heaphax
Devs have to somehow try to evade/exploit the new memchunkhdr security to be able to use heaphax
But for my understanding it's still there...
I suggest you read the heaphax part of it (specially the one who explains that if it has been fixed or not) here.Uh, no. That's memchunkhax2.1, a full blown arm11 kernel exploit. This isn't that, it's a service takeover to get legit CIA installation without kernel access.
I must be confused... I thought heaphax was just another name for snshax. snshax is just spawning 2 instances of ns pushing it below the gspwn cutoff. It has nothing to do with memchunks... Right?I suggest you read the heaphax part of it (specially the one who explains that if it has been fixed or not) here.
It could be using some memchunk parts, maybe this is snshax 2.0? XDI must be confused... I thought heaphax was just another name for snshax. snshax is just spawning 2 instances of ns pushing it below the gspwn cutoff. It has nothing to do with memchunks... Right?
im sure there are 2-3 arm 11 kernel exploits but they're not released publiclyYeah because legit cia installation would be a big step up for 11.0
memchunkhaxTrying to revive a patched exploit is stupid, there are plenty other exploits in kernel11, it'd be smarter to try to take one of them over.
it's already possible... afaik, ctr-httpwn still isn't patched...Yeah because legit cia installation would be a big step up for 11.0