Hacking HENkaku for 3.67 still releasing in 1-2 years

[Lia]

No major changes in 3.68 except for TLS v1.2 support. This means that the HENkaku exploit for 3.67 and below has not been patched and therefore will be releasing around Vita EOL, in around 1 to 2 years.

A kernel bug was fixed, however the HENkaku exploit was not affected.

If you're on 3.67, it's safe to update.
If you're on 3.65 or below, do not update. Start blocking updates using this guide.
If you're on 3.60 or below, follow vita.cfw.guide to install HENkaku and HENkaku Enso.

Source

 

[8BitWonder]

Glad to hear Sony hasn't smashed the bug quite yet. It's too bad enso won't work above 3.65, though I'm sure many won't mind non-persistence if it means homebrew on the latest fw.

 

[Darksabre72]

Glad to hear Sony hasn't smashed the bug quite yet. It's too bad enso won't work above 3.65, though I'm sure many won't mind non-persistence if it means homebrew on the latest fw.

the flow stated something about sony fixed a kernel bug, but im guessing he is still exploring the vita so take this with a grain of salt: https://twitter.com/theflow0/status/984918354346627072

 

[8BitWonder]

the flow stated something about sony fixed a kernel bug, but im guessing he is still exploring the vita so take this with a grain of salt: https://twitter.com/theflow0/status/984918354346627072

Seems like he definitely has Henkaku working though.
Mayhaps they patched one of the three non-exploitable kernel bugs he found earlier.

well of course I am already running henkaku on 3.68 in order to decrypt the kernel modules and analyse them

— Andy Nguyen (@theflow0) April 13, 2018

 

[Darksabre72]

Seems like he definitely has Henkaku working though.
Mayhaps they patched one of the three non-exploitable kernel bugs he found earlier.
https://twitter.com/theflow0/status/984936002941747201

it seems that the flow will definitely wait until next year

 

[Deleted User]

LOL at people who put random dates with no meaning on everything.

I've seen it done too often in the home-brew community.

 

[8BitWonder]

Looks like more was patched than TheFlow saw at first.
Seems Sony was busy patching up devkits. A shame to lose kernel execution on devkits, but at least Henkaku can still be run on 3.68.

I was wrong with my statements about 3.68. First of all TLSv1.2 was added in 3.67 and secondly Sony has fixed 3 kernel bugs in 3.68, which combined, could lead to kernel code execution on a devkit.

— Andy Nguyen (@theflow0) April 14, 2018

 

[Darksabre72]

LOL at people who put random dates with no meaning on everything.

I've seen it done too often in the home-brew community.

the flow said that he would release the exploit late this year or next year, and that depends if sony patches the exploit that the flow found on 3.67

 

[Tony_93]

the flow said that he would release the exploit late this year or next year, and that depends if sony patches the exploit that the flow found on 3.67

When did he say that his release was dependent on the wxploit being patched again? Or you are just making that up...

 

[8BitWonder]

When did he say that his release was dependent on the wxploit being patched again? Or you are just making that up...

what's the reason to wait if it's fixed?

— Andy Nguyen (@theflow0) April 10, 2018

 

[Chelsea_Fantasy]

Seems like he definitely has Henkaku working though.
Mayhaps they patched one of the three non-exploitable kernel bugs he found earlier.
https://twitter.com/theflow0/status/984936002941747201

Yeah, but he is running HENkaku 3.68 on a Devkit, not a retail one:

Looks like more was patched than TheFlow saw at first.
Seems Sony was busy patching up devkits. A shame to lose kernel execution on devkits, but at least Henkaku can still be run on 3.68.
https://twitter.com/theflow0/status/985137344570372096

 

[8BitWonder]

Yeah, but he is running HENkaku 3.68 on a Devkit, not a retail one:

Are you sure? It sounds like he has it running on retail if his kernel bugs on devkit were patched.
Plus it sounds like he would have released the retail exploit if it was patched.

 

[Tony_93]

@8BitWonder That tweet means that the release could be sooner if the exploit is patched before the intended release date.

That doesn't mean TheFlow plans to release the exploit around december/next year only if it gets patched as implied above.

 

[Chelsea_Fantasy]

Are you sure? It sounds like he has it running on retail if his kernel bugs on devkit were patched.
Plus it sounds like he would have released the retail exploit if it was patched.

yes I am sure:
https://twitter.com/theflow0/status/984923239892881414
and
https://twitter.com/theflow0/status/984919058863845378

 

[8BitWonder]

yes I am:
https://twitter.com/theflow0/status/984923239892881414
and
https://twitter.com/theflow0/status/984919058863845378

Hmm, I think I'm starting to understand. Because he released a patched exploit for devkits on 3.67 and below, he must still have Henkaku running on devkit 3.68 to check that it was fixed.

However I think it's pretty safe to say he has it running on retail too. Here he says he has kernel execution up to 3.67 (on what is assumed to be retail, because he did it without a devkit):
https://twitter.com/theflow0/status/965261396681338880
And in the tweet I linked earlier he made it clear that he would release the exploit if it was patched:
https://twitter.com/theflow0/status/983759031570444288

Seeing that he hasn't released the retail 3.67 exploit, it can still be assumed that it hasn't been patched, and works on 3.68 as well.

 

[Chelsea_Fantasy]

However I think it's pretty safe to say he has it running on retail too. Here he says he has kernel execution up to 3.67 (on what is assumed to be retail, because he did it without a devkit):
https://twitter.com/theflow0/status/965261396681338880

he was ambiguous, could be anything...

And in the tweet I linked earlier he made it clear that he would release the exploit if it was patched:
https://twitter.com/theflow0/status/983759031570444288

Yes, patched in both, normal and devkit, if still working on devkit, it means it is not completely patched as they found a workaround to jump over it, but not a way to patch it. Also, he could be planning on releasing the 3.67 one later with proper work.

Do not get you hopes to high, but as it seems, 3.68 is almost dead on retail consoles...

 

[8BitWonder]

Do not get you hopes to high, but as it seems, 3.68 is almost dead on retail consoles...

On that note we certainly agree. Sony is likely hard at work plugging any remaining holes there might be in their security.
Though even if a 3.67 or 3.68 retail kexploit were to drop, I'll go no further than 3.65. I love enso too much to let it go.

 

[Chelsea_Fantasy]

On that note we certainly agree. Sony is likely hard at work plugging any remaining holes there might be in their security.
Though even if a 3.67 or 3.68 retail kexploit were to drop, I'll go no further than 3.65. I love enso too much to let it go.

I guess you will sooner or later drop it, as sooner or later, newer games will come to 3.67+ and I guess you have a PSVita to play games, right?
But anyway, I think Sony know that holes on PSV can be used in PS4, so, they want them patched.

 

[8BitWonder]

I guess you will sooner or later drop it, as sooner or later, newer games will come to 3.67+ and I guess you have a PSVita to play games, right?
But anyway, I think Sony know that holes on PSV can be used in PS4, so, they want them patched.

I personally use mine as a small emulation station, and with 3.65 content now accessible to 3.60 users I have everything I've been interested in vita-wise. So no plans on dropping it anytime soon.

 

[Chelsea_Fantasy]

I personally use mine as a small emulation station, and with 3.65 content now accessible to 3.60 users I have everything I've been interested in vita-wise. So no plans on dropping it anytime soon.

I will not say that ALL the content is accessible on 3.60, as, by example, Darkest Dungeon crashes on 3.60 randomly (I personally make a MaiDump of my own PSN game for a friend and did not worked as intended). Later I tried Game + Update + DLC (the only DLC I have) and worst result, game crashes on launch. You need to set it to mode 4 to work, so, no compatibility with DLCs...

Anyway... if you have it as an emulation station, you are ready to go!