Why different homebrew PKGs between official 3.41 and 3.55?

**Ben Jeremy** · 01-15-2011,07:49 PM

OK, why do we have to install different packages (and presumably the selfs are signed differently?) between 3.41 and 3.55? If we can properly sign the selfs, shouldn't they work regardless of the firmware, once installed (in jailbroken 3.41 or Geohot 3.55)? Or am I mistaken, and the selfs, once installed, work with both, and only the PKGs are the issue here?

The last seems the most likely, if we have a working makeself.

Wondering about this...

**sonnyz** · 01-15-2011,08:58 PM

Good question, I've wondered the same thing. I would imagine that the 3.41 eboots would work on all future firmwares. It wouldn't make sense to me otherwise.

**Ben Jeremy** · 01-15-2011,09:11 PM

I'm guessing that if I go through the trouble, both 3.41 and 3.55 executables will be identical... that the PKGs are different.

You can't install Geohot 3.55 PKGs in jailbroken 3.41 consoles.

For what I'm looking to do, I don't need PKG files - I'm planning on creating some lv2diag.self files to diagnose bricks and maybe do some cleanup on the XMB logs.

**sabin1981** · 01-15-2011,09:35 PM

Likewise! I've been wondering about this since the very start; WHY can't we install packages signed for Geohot's version of 3.55, on lower firmwares such as 3.41? These 3.55 packages work in JB mode or retail - so why not 3.41 JB/Retail?

**daxtsu** · 01-16-2011,04:15 AM

Originally Posted by sabin1981

Likewise! I've been wondering about this since the very start; WHY can't we install packages signed for Geohot's version of 3.55, on lower firmwares such as 3.41? These 3.55 packages work in JB mode or retail - so why not 3.41 JB/Retail?

From what I understand, it's the way the packages are signed. package_finalize(the tool that makes them compatible with MFW 3.55) signs the PKG as a pseudoretail package(retail with not all the right things signed? I'm still unsure), which I guess can't be read by OFWs such as 3.41. Or it could be as simple as being signed by 3.55's keys, which 3.41 obviously would not have. Otherwise, if you can extract the PKG, the eboot.bin will run fine on any firmware. Also, 3.41 packages are signed to be debug PKGs, aren't they?

**Saner** · 01-16-2011,04:18 AM

geohot removed the need for the pkg to be signed on his firmware.

thats why you can install it on that, but cant install it on (un jailbroken) 3.41

It runs because everything inside the PKG is signed.

this is a IRIC of course

**daxtsu** · 01-16-2011,04:22 AM

That too. He removed certain signing checks.

**ken_oh** · 01-16-2011,04:23 AM

I don't think it's the signing alone.. this is because iv'e signed many eboot pkg files and they work fine.. but when i tried installing a re-signed fbanext pkg (latest version 3.41) it didn't install.. so i just have to keep the older working version (3.55 signed version of it).. this kinda thin baffels me

**subcon959** · 01-16-2011,04:24 AM

Yeah, the only difference is that package_finalize step. Is there anyway to reverse that? A lot of stuff seems to be released this way, killing 3.41 compatibility. It seems it would make more sense to release the 3.41 package and give people the option to 'finalize' it if needed.

**mеdi01** · 01-16-2011,04:29 AM

OK, my 2 cents:

1) PKG signing key is NOT part of epic.fail.sony (tm). Which means, we can NOT sign PKG files for OFW.
2) Geohot, to my understanding, didn't drop signature check, just added his own key.. 3.55 pkg-s are signed with his key (by his tool)
3) PKG signature is only checked, when installing stuff, not when running.
4) 3.41 PKGs aren't signed at all

User Tag List

Thread: Why different homebrew PKGs between official 3.41 and 3.55?

Tweet

LinkBack

Thread Tools

Display


	Would you like to get all the new info from PSX-Scene in your email each day? Subscribe to our Daily Digest! Want to learn more about the team keeping you up to date with the latest scene news? Read about them now! Check out our Developer bios, too!