After a night of partying to ring in the New Year of 2011, we wake up to the fact that scene developers don't seem to sleep or party, as they were busy posting and tweeting out some of the major PS3 KEYS that will soon unlock the doors to make your PS3 a totally open book to developers!
First we found two new gifts left in our PSX-SCENE forums again by geohot, one gives developers two of the much needed v3.41 metldr keys as "simple proof", and then later on geohot uploads geoldr as a Happy New Year Day Gift to scene developers in helping them to get more amazing things done in the PS3 world, which I have attached to this post!
Next going thru all the tweets we missed while having a good time over New Year's Eve, we find that the now world famous new Team fail0verflow had released some of the much needed SHA1 hashes via their twitter account:
And also Mathieulh was busy tweeting during New Year's Eve with a bunch of LV2LDR keys:@fail0verflow said:
Private Pastie <-- sha1 hashes for some keys
Sony seem to have just randomly sprinkled crypto on the PS3 as magical pixie dust. Wackier crypto usage MUST be more secure, right? Right?
Code:a3d8fbcf120177844c848c72afe8bf7e5fa29ab4 iso-ctype-315 287e056ab77c7a10ec73108e63f12b811ff0f888 iso-iv-315 161e5c4ca0064bddf445c19d89f703384e504f41 iso-key-315 9739847f294d869b4c73fc8115be3f60cf660c4c iso-priv-315 755d0f717cf0af17f60ef0810a45009245869b5c lv2-ctype-315 1160bc28c9547067c7b5d3661b822290a1474d9f lv2-iv-315 9aa78cc3d63be7858a875819717f3965527dd046 lv2-key-315 73340c5b90402552b333331e9b4189c1cae6e9ba lv2-priv-315 94fba8ed9675ee9d55dc6dc220b26bb162eb6ccc spp-ctype-315 8ba0748dc57f79ce508bda47633c01897175008b spp-iv-315 160d0eac80f0750c3afcfdde3070e75fa5fff864 spp-key-315 87fef0cbf46e06c4fa592d6e4f3f1bf4c9f7fca1 spp-priv-315 b5ab517f7f92cc8604f9e08ebf09e545a06c454d pkg-ctype-315 ff6b278b7993cccd82837abe8f46a228a93931f4 pkg-iv-315 78624dbfa916a34655678e2eb41ab232156a4acf pkg-key-315 70e4aa4864197ad39d9226d4c55ea345aa2de287 pkg-priv-315 e1fbd73372cbd3708c1cbe8f95aa2eedeee70406 rvk-ctype-315 3003dcb2385cc8a60fa3566a2cc0e7a76fde680a rvk-iv-315 e1468a087ecc12af0393b811f826a1bfe23cc891 rvk-key-315 bd20f3764db0d29898f3cb72bababbe73b4b3332 rvk-priv-315
But Mathieulh was not finished tweeting, he later followed up the next day with a bunch of appldr keys:Twitlonger @Mathieulh said:
Lv2ldr keys:
Decrypts all the External lv2 versions from pre 1.00 to anything below 3.40.Code:erk: 94303F69513572AB5AE17C8C2A1839D2C24C28F65389D3BBB11894CE23E0798F riv: 9769BFD187B90990AE5FEA4E110B9CF5
Use the algorithm available here: https://ps3wiki.lan.st/index.php/Self_Crypto and here: https://ps3wiki.lan.st/index.php/SEL...and_Decryption
You can also use this: https://github.com/ooPo/ps3sdk To perform the decryption.
Maybe more to come. They allow to decrypt lv2, the ps2 emus and to resign.
That is, IF you get K, which you calculate using 2 different lv2 binaries, then you can flash a pre 3.40 lv2ldr and use your lv2_kernel.self with it.
Many thanks to all of our valued PSX-SCENE members that made 2010 a great yearTwitlonger @Mathieulh said:
A little update to the application loader keys I posted earlier:
Revision 0 keys used in from 0.80 to 0.92
Revision 1 keys used from 0.95 to 3.31 and in updatersCode:erk-rev0 95F50019E7A68E341FA72EFDF4D60ED376E25CF46BB48DFDD1F080259DC93F04 riv-ev0 4A0955D946DB70D691A640BB7FAECC4C
Unknown keys, seem not to be in use.Code:erk-rev1 79481839C406A632BDB4AC093D73D99AE1587F24CE7E69192C1CD0010274A8AB riv-rev1 6F0F25E1C8C4B7AE70DF968B04521DDA
Enjoy! - Credits: Graf_Chokolo, RichDevX, Mathieulh, N_D_T, TitanMKD -CheersCode:erk-unk1 4F89BE98DDD43CAD343F5BA6B1A133B0A971566F770484AAC20B5DD1DC9FA06A riv-unk1 90C127A9B43BA9D8E89FE6529E25206F erk-unk2 AAC20B5DD1DC9FA06A90C127A9B43BA9D8E89FE6529E25206F8CA6905F46148D riv-unk2 7D8D84D2AFCEAE61B41E6750FC22EA43 erk-unk3 D91166973979EA8694476B011AC62C7E9F37DA26DE1E5C2EE3D66E42B8517085 riv-unk3 DC01280A6E46BC674B81A7E8801EBE6E erk-unk4 F9EDD0301F770FABBA8863D9897F0FEA6551B09431F61312654E28F43533EA6B riv-unk4 A551CCB4A42C37A734A2B4F9657D5540
P.S. The self revision is located at 0x00000009 in the self header, it defines the key set in use.to 2011!


LinkBack URL
About LinkBacks



to 2011!







