I think memchunkhax2.1 is more suitableBut it has nothing to do with Memchunkhax1 or 2.
It wouldn't. Its not an exploit for that, its an exploit using svcbackdoor. Svchax would be much better.I think memchunkhax2.1 is more suitable
One more word outta you...!I think this vuln should've been kept private until...
it is based on memchunkhax2 , just modified to get past the 'fix' added in 10.4.@aliaspider How does this work? I thought you can't call svcBackdoor without special permissions.
Like meWe kernel hax now... again... yeah, cool?
I guess it's a chance for the people who accidentally went to 10.6.
& Knucklesmemchunkhax3!
I thought it but with thisAnd I said another kernel hax would only happen in a year... Good job, amazing work.