What makes a permanent PS4 Jailbreak difficult?

  • Thread starter Thread starter Dopam1ne
  • Start date Start date
  • Views Views 9,959
  • Replies Replies 6
  • Likes Likes 1

Dopam1ne

Active Member
Newcomer
Joined
Dec 15, 2018
Messages
38
Reaction score
9
Trophies
0
XP
295
Country
United Kingdom
My Vita is Permanently Jailbroken, so is my 3ds :) Can anyone explain to me what makes this a more challenging feat with the PS4?
 
  • Like
Reactions: Kazmar
It has todo with the nature of a bug.
A boot process consists of multiple layers. See each layer as an entity in a company:
- The boss (bootloader)
- Manager (kernel)
- Employee (userspace)
And we need to bribe a person in order to hack the system.

Depending on the system the managers/employees will be as new each reboot and each update. The boss handles the reboot process and does not get wiped each boot. We need a bootloader bug to enable a rebootable exploit. But as you might guess, a the boss is really hard to bribe.
Most exploits go from down to upper management: userspace -> kernel -> HAXX. But in rare cases we find a bootloader / bigger exploit. These are EXTREMELY rare these days. Like once every 10 years kind of rare, or a LOT of money kind of rare. People who find these will not hand these out for free anymore as they can be worth $$$$.

There are a lot of systems/variations so this example might not fly well for all. Moral of the story: we need unpatchable bugs.
 
It has todo with the nature of a bug.
A boot process consists of multiple layers. See each layer as an entity in a company:
- The boss (bootloader)
- Manager (kernel)
- Employee (userspace)
And we need to bribe a person in order to hack the system.

Depending on the system the managers/employees will be as new each reboot and each update. The boss handles the reboot process and does not get wiped each boot. We need a bootloader bug to enable a rebootable exploit. But as you might guess, a the boss is really hard to bribe.
Most exploits go from down to upper management: userspace -> kernel -> HAXX. But in rare cases we find a bootloader / bigger exploit. These are EXTREMELY rare these days. Like once every 10 years kind of rare, or a LOT of money kind of rare. People who find these will not hand these out for free anymore as they can be worth $$$$.

There are a lot of systems/variations so this example might not fly well for all. Moral of the story: we need unpatchable bugs.
That is a really great explanation and I love the analogy.
 
  • Like
Reactions: AfricanLuigi
It has todo with the nature of a bug.
A boot process consists of multiple layers. See each layer as an entity in a company:
- The boss (bootloader)
- Manager (kernel)
- Employee (userspace)
And we need to bribe a person in order to hack the system.

Depending on the system the managers/employees will be as new each reboot and each update. The boss handles the reboot process and does not get wiped each boot. We need a bootloader bug to enable a rebootable exploit. But as you might guess, a the boss is really hard to bribe.
Most exploits go from down to upper management: userspace -> kernel -> HAXX. But in rare cases we find a bootloader / bigger exploit. These are EXTREMELY rare these days. Like once every 10 years kind of rare, or a LOT of money kind of rare. People who find these will not hand these out for free anymore as they can be worth $$$$.

There are a lot of systems/variations so this example might not fly well for all. Moral of the story: we need unpatchable bugs.
Thank you for the streamlined explanation instead of being a jerk :p Makes a ton of sense now
 
@KirovAir Great explanation!

This and Sony learned a lot from their bout with the ps3 security. Seems they really tightened things up quite a bit in that department after the ps3 mishap.
 
  • Like
Reactions: KiiWii

Site & Scene News

Popular threads in this forum