Post: Why CFW 3.56 Is Not Possible
Options
01-30-2011, 04:21 PM
#1
Newelly
Guest
Here Is A Quote From A Private Blog.. I Will Not Be Posting The Blog
This Is The Reason Why 3.56 CFW Is Strictly Not Possible ... As Of Yet Anyways..
[/b]
Originally posted by another user
Hi, I’m rms, a PS3 software/homebrew developer.
Well, I’ve been on EFnet for a while now, and I’ve seen many people asking about PS3 Custom Firmware 3.56,
well, let me put it in a simple manner, it’s not possible thanks to what Sony did with their ECDSA (Elliptic Curve DSA) cryptography,
and the new PUP format along with Cell-OS Lv2 having some extra checks on SELF files now.
See, when we used to get private keys for earlier fail ECDSA keyset revisions,
a variable, r, in the ECDSA signature was static, thus allowing us to get the keys using the signature itself,
now, Sony fixed this by making that variable random, so we can no longer use simple algebra to get the private key like before.
Do note that to retrieve the older private keys, one needed to use 2 signatures, and simply compare them to get the private key. Now,
for those who do not know about private keys and public keys and ERK/RIV, here’s a simple explanation: Private keys are used to create signatures,
public keys are used to verify the signature’s authenticity. ERK/RIV is used to decrypt the encrypted SELF data.
The new PUP format has 2 extra files, one consists of a new tarball with spkg_hdr1 files,
ensuring package integrity, so one can no longer create rehashed pups anymore. Until the spkg format is deciphered,
and they can be resigned, one’s pretty much stuck with Official Firmware. Core OS also has some new additions,
appldr now checks your SELF revision for NPDRM, and Lv2 selfs, they either must be whitelisted or use the new revision 0x0D keyset in 3.56.
Lv2 now will also refuse to load older updater or Lv2diag.self files that do not use the 0x0D keyset. Core OS also has two new revoke lists,
prog_srvk and pkg_srvk. They have yet to be fully inspected yet.
So, in the end, Sony pretty much fixed most of the fail, some’s still around though, go look for it. =)
//I Also Have Some Keys If Someone Wants Them Pm Me
//Source Is A Private Blog.. If Mod / Admin Wants It For Approval Pm Me Thanks...
Image:
Of My Question To rms And His Reply..
You must login or register to view this content.
The following 2 users say thank you to Newelly for this useful post:
01-30-2011, 08:32 PM
#21
inthezoneac
Gobble
all I used CFW was for emulators, not a big deal that I updated, still have my CFW psp for that.
I just hope some of you weren't doing it for "back ups", simpling stealing from developers/publishers.
I just hope some of you weren't doing it for "back ups", simpling stealing from developers/publishers.
01-31-2011, 02:31 AM
#22
zen10786
Haxor!
Anything possible , they said the same about 3.51 and about the ps3 but still we got there . If some one can make the security Then why cart some break it . Am not one of them people but hope that may I could be . I think Sony might have the latest tech but there one thing they not got is a family like us we might not alway see eye to eye but we still work as a family help each other . Black ops security will flop so will Sony .
01-31-2011, 06:22 AM
#23
xSimpleHeartz
I am error
My tiny brain cannot understand what rms just said. /facepalm
01-31-2011, 09:15 AM
#24
Gloxin
Bounty hunter
PRIVATE BLOG??? lol....NICE TRY BUDDY
The Road Ahead. Dead End Or Roadblock..? (from a Tweet by RMS)
The road ahead
Posted on January 30, 2011 by rms
Hi, I’m rms, a PS3 software/homebrew developer.
Well, I’ve been on EFnet for a while now, and I’ve seen many people asking about PS3 Custom Firmware 3.56, well, let me put it in a simple manner, it’s not possible thanks to what Sony did with their ECDSA (Elliptic Curve DSA) cryptography, and the new PUP format along with Cell-OS Lv2 having some extra checks on SELF files now.
See, when we used to get private keys for earlier fail ECDSA keyset revisions, a variable, r, in the ECDSA signature was static, thus allowing us to get the keys using the signature itself, now, Sony fixed this by making that variable random, so we can no longer use simple algebra to get the private key like before. Do note that to retrieve the older private keys, one needed to use 2 signatures, and simply compare them to get the private key. Now, for those who do not know about private keys and public keys and ERK/RIV, here’s a simple explanation: Private keys are used to create signatures, public keys are used to verify the signature’s authenticity. ERK/RIV is used to decrypt the encrypted SELF data.
The new PUP format has 2 extra files, one consists of a new tarball with spkg_hdr1 files, ensuring package integrity, so one can no longer create rehashed pups anymore. Until the spkg format is deciphered, and they can be resigned, one’s pretty much stuck with Official Firmware. Core OS also has some new additions, appldr now checks your SELF revision for NPDRM, and Lv2 selfs, they either must be whitelisted or use the new revision 0x0D keyset in 3.56. Lv2 now will also refuse to load older updater or Lv2diag.self files that do not use the 0x0D keyset. Core OS also has two new revoke lists, prog_srvk and pkg_srvk. They have yet to be fully inspected yet.
So, in the end, Sony pretty much fixed most of the fail, some’s still around though, go look for it. =)
PSX-SCENE
The Road Ahead. Dead End Or Roadblock..? (from a Tweet by RMS)
The road ahead
Posted on January 30, 2011 by rms
Hi, I’m rms, a PS3 software/homebrew developer.
Well, I’ve been on EFnet for a while now, and I’ve seen many people asking about PS3 Custom Firmware 3.56, well, let me put it in a simple manner, it’s not possible thanks to what Sony did with their ECDSA (Elliptic Curve DSA) cryptography, and the new PUP format along with Cell-OS Lv2 having some extra checks on SELF files now.
See, when we used to get private keys for earlier fail ECDSA keyset revisions, a variable, r, in the ECDSA signature was static, thus allowing us to get the keys using the signature itself, now, Sony fixed this by making that variable random, so we can no longer use simple algebra to get the private key like before. Do note that to retrieve the older private keys, one needed to use 2 signatures, and simply compare them to get the private key. Now, for those who do not know about private keys and public keys and ERK/RIV, here’s a simple explanation: Private keys are used to create signatures, public keys are used to verify the signature’s authenticity. ERK/RIV is used to decrypt the encrypted SELF data.
The new PUP format has 2 extra files, one consists of a new tarball with spkg_hdr1 files, ensuring package integrity, so one can no longer create rehashed pups anymore. Until the spkg format is deciphered, and they can be resigned, one’s pretty much stuck with Official Firmware. Core OS also has some new additions, appldr now checks your SELF revision for NPDRM, and Lv2 selfs, they either must be whitelisted or use the new revision 0x0D keyset in 3.56. Lv2 now will also refuse to load older updater or Lv2diag.self files that do not use the 0x0D keyset. Core OS also has two new revoke lists, prog_srvk and pkg_srvk. They have yet to be fully inspected yet.
So, in the end, Sony pretty much fixed most of the fail, some’s still around though, go look for it. =)
PSX-SCENE
01-31-2011, 01:45 PM
#26
rms_ps3dev
Guest
Originally posted by Gloxin
PRIVATE BLOG??? lol....NICE TRY BUDDY
The Road Ahead. Dead End Or Roadblock..? (from a Tweet by RMS)
The road ahead
Posted on January 30, 2011 by rms
Hi, I’m rms, a PS3 software/homebrew developer.
Well, I’ve been on EFnet for a while now, and I’ve seen many people asking about PS3 Custom Firmware 3.56, well, let me put it in a simple manner, it’s not possible thanks to what Sony did with their ECDSA (Elliptic Curve DSA) cryptography, and the new PUP format along with Cell-OS Lv2 having some extra checks on SELF files now.
See, when we used to get private keys for earlier fail ECDSA keyset revisions, a variable, r, in the ECDSA signature was static, thus allowing us to get the keys using the signature itself, now, Sony fixed this by making that variable random, so we can no longer use simple algebra to get the private key like before. Do note that to retrieve the older private keys, one needed to use 2 signatures, and simply compare them to get the private key. Now, for those who do not know about private keys and public keys and ERK/RIV, here’s a simple explanation: Private keys are used to create signatures, public keys are used to verify the signature’s authenticity. ERK/RIV is used to decrypt the encrypted SELF data.
The new PUP format has 2 extra files, one consists of a new tarball with spkg_hdr1 files, ensuring package integrity, so one can no longer create rehashed pups anymore. Until the spkg format is deciphered, and they can be resigned, one’s pretty much stuck with Official Firmware. Core OS also has some new additions, appldr now checks your SELF revision for NPDRM, and Lv2 selfs, they either must be whitelisted or use the new revision 0x0D keyset in 3.56. Lv2 now will also refuse to load older updater or Lv2diag.self files that do not use the 0x0D keyset. Core OS also has two new revoke lists, prog_srvk and pkg_srvk. They have yet to be fully inspected yet.
So, in the end, Sony pretty much fixed most of the fail, some’s still around though, go look for it. =)
PSX-SCENE
The Road Ahead. Dead End Or Roadblock..? (from a Tweet by RMS)
The road ahead
Posted on January 30, 2011 by rms
Hi, I’m rms, a PS3 software/homebrew developer.
Well, I’ve been on EFnet for a while now, and I’ve seen many people asking about PS3 Custom Firmware 3.56, well, let me put it in a simple manner, it’s not possible thanks to what Sony did with their ECDSA (Elliptic Curve DSA) cryptography, and the new PUP format along with Cell-OS Lv2 having some extra checks on SELF files now.
See, when we used to get private keys for earlier fail ECDSA keyset revisions, a variable, r, in the ECDSA signature was static, thus allowing us to get the keys using the signature itself, now, Sony fixed this by making that variable random, so we can no longer use simple algebra to get the private key like before. Do note that to retrieve the older private keys, one needed to use 2 signatures, and simply compare them to get the private key. Now, for those who do not know about private keys and public keys and ERK/RIV, here’s a simple explanation: Private keys are used to create signatures, public keys are used to verify the signature’s authenticity. ERK/RIV is used to decrypt the encrypted SELF data.
The new PUP format has 2 extra files, one consists of a new tarball with spkg_hdr1 files, ensuring package integrity, so one can no longer create rehashed pups anymore. Until the spkg format is deciphered, and they can be resigned, one’s pretty much stuck with Official Firmware. Core OS also has some new additions, appldr now checks your SELF revision for NPDRM, and Lv2 selfs, they either must be whitelisted or use the new revision 0x0D keyset in 3.56. Lv2 now will also refuse to load older updater or Lv2diag.self files that do not use the 0x0D keyset. Core OS also has two new revoke lists, prog_srvk and pkg_srvk. They have yet to be fully inspected yet.
So, in the end, Sony pretty much fixed most of the fail, some’s still around though, go look for it. =)
PSX-SCENE
hi.
rms here.
want to know why its really hard to make custom sprx files now ? its because r in the ecdsa signature is random. it was simple formula manipulation to get the keys for earlier selfs, 8th grade algebra to be honest, you just do a little math magic. there are other fail issues in lv2, its like swiss cheese, just look for them. this ecdsa fail gave you people to every level of the system except for lv0, on earlier firmware. sure you can patch other core os things, but, what about testing. we dont want another wankybrick do we ?
now, before you self proclaimed hackers think of making custom firmware, think of learning about the system, i know i did. it helped tons to already know programming, crypto, and powerpc64 asm. trust me, it really helps.
no, i am not a troll, i know programming, and i do it regularly.
and my twitter is You must login or register to view this content.
no one else.
oh, and i do not play any games on my ps3. i use it for linux.
The following user thanked rms_ps3dev for this useful post:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
