Cool, try this version @chicco33 some of the features related to join/split iso in the last 2 managunz versions was made because your suggestions, please check if all that join/split functions are working fine, i guess you are the best that can test that

Managunz doesnt works on HAN, as a general rule of what works in HAN and what doesnt works... you shoud think in the concept of "executable files" (like an .exe in windows)
In HAN only works the executables signed by sony... but all other executables signed unnofficially (scene apps) are not going to work because doesnt passes the signature check
Is imposible to bypass this signature check in HAN... by now

In PS3 the executable files are EBOOT.BIN, SELF and SPRX files... this ones are a "cant touch this"

Partially. We can decrypt those sprx files, we can encrypt those files. But we can't add correct ecdsa signature to them. CFW have those ecdsa check patched so it accept those sprx files.

"as far as i know" But I can be wrong here.

Is also related with the fact that there are used 2 "keysets", a set is used to encrypt (this never goes out of sony facilities) and another set to decrypt (included in all ps3)

The ones for decrypting are public, we can decrypt everything because there was a point where sony stopped updating them
But for encrypting we only have the keysets that was taken from pre 3.55 firmwares

The keys used for decrypting are derived from the keys used for encrypting (so are related... you can think in them as a parent-children relationship) Theoretically is not be posible to find the "parent" by looking at the "children"... but sony made a mistake that allowed people to deduce them

All this is about cryptography, and i dont understand it, so take this explain as a grain of salt in plain words, maybe i said some incorrection

kozarovv's post is correct.
ECDSA encryption/decryption relies on a pair of keys, one private & one public.
The private keys are used to encrypt the files at source & the paired public key is used to decrypt & validate that the files were not tampered with.
We only have the private keys up to 3.55 leaked years ago.
So in practice we can decrypt 4.xx /dev_flash sprx and self files & we can patch the files without problems but we can only reencrypt them with the private keys we currently have.
Post 3.56 loaders will detect & reject all /dev_flash executable files reencrypted with old private keys, considered invalid.
A CFW works around this by patching the loaders to remove the ecdsa checks..

THE GENERAL RULE OF THUMB IF IT WORKS FOR HAN IT WILL SAY IT WILL WORK WITH HAN.. HAS SOMETHING BEEN RELEASED WITHOUT SAYING IT WAS FOR HAN??? NO

SO PLEASE CAN WE STOP IS THIS FOR HAN ON EVERY THREAD..

IF IT's FOR HAN, IT WILL BE NOTED IT's FOR HAN......
IF IT's NOT NOTED , IT's NOT FOR HAN..

Very Simple Concept ..

This news mentions NOTHING about HAN.
So we can conclude what?? ______ (hint this is not for HAN)

Clue #2 to often look at as well:
If the term PS3 Homebrew is used (That means its a Homebrew App) HAN does not play PS3 Homebrew (only limited homebrew of the PS1/PS2 era through the unlocked internal emulators )

Let me fix that sentence, this way sounds better