Post: Possible encryption exploit
03-04-2011, 05:10 AM #1
Norman
NORMAN
(adsbygoogle = window.adsbygoogle || []).push({}); Alright so what we first need to cover is the requirements


1 reveres engineering skills.
2 basic knolage of encryption/decryption
3 an innovating brain.



Alright so the exploit is as following

1 we Need to first find a eboot that is not npdrm encrypted.

2 we take the self and decrypt it using the 3.56 public keys.

3 we take the original .self, and the new .elf (this is where it gets controversial.) and we put them in some program that can calculate the keys from a before/after scenario. So it would see what the elf is, and compare the elf with the self, to find the algorthim it uses to encrypt the elf.



Elf= unencrypted self
Self= encrypted executable.


This seems like a method that could work, but then agai could it really be that easy?
(adsbygoogle = window.adsbygoogle || []).push({});
03-04-2011, 02:26 PM #11
Norman
NORMAN
Originally posted by CoDax View Post
See there is no way to access the files on 3.56 unless someone has a SATA which can be costly. So yah this exploit is possible but for everyone to do it we would need SATA drives. and no one feels like going to amazon and buying one :\
But it is a good possible idea.

---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------



We found the keys its just no one knows how to sign with them yet.


What I was thinking is using the any hdd on your ps3. If you don't know that method it's where you change the hdd number on you registry.
03-04-2011, 06:04 PM #12
zxz0O0
Are you high?
Wont work. You can NOT calculate the keys anymore
03-04-2011, 06:34 PM #13
0xFa1z
Splicer
Originally posted by norman View Post
What I was thinking is using the any hdd on your ps3. If you don't know that method it's where you change the hdd number on you registry.


There are bit size restrictions... this wont take u no where, u still need a modified xml channel for it to load, and how do u get that? CFW
03-04-2011, 08:21 PM #14
CyberNomadic
Web Developer
Originally posted by izyehboy View Post
The actual "END" key for allowing homebrew isnt released. If it was, where's the CFW's? Signing isnt the problem, the keys are...


Yes we have the keys its just that we dont have the private key that is why signing is a problem:\
03-04-2011, 08:57 PM #15
Norman
NORMAN
Originally posted by 0xFa1z View Post
There are bit size restrictions... this wont take u no where, u still need a modified xml channel for it to load, and how do u get that? CFW


We could use cfw because the objective is to get a 3.56 file from the ps3 to a 3.55 ps3 so yes we could get files from and too the 3.56 ps3.
03-05-2011, 07:32 AM #16
0xFa1z
Splicer
Originally posted by norman View Post
We could use cfw because the objective is to get a 3.56 file from the ps3 to a 3.55 ps3 so yes we could get files from and too the 3.56 ps3.

As much as i hate saying this, but just give up, there are restrictions, go a head and try and then tell me.
03-05-2011, 09:35 AM #17
izyehboy
Treasure hunter
Originally posted by CoDax View Post
Yes we have the keys its just that we dont have the private key that is why signing is a problem:\


Then we dont have the keys now do we?

9 out of 10 isnt 10 out of 10.
03-05-2011, 10:41 AM #18
ρrodigyz
Cool story bro!
Alright lets do this! Give me a few server computers, a few years, and then we'll finally crack the private RSA key.
03-05-2011, 10:54 PM #19
CyberNomadic
Web Developer
Originally posted by izyehboy View Post
Then we dont have the keys now do we?

9 out of 10 isnt 10 out of 10.


OK LET ME PUT THIS IN 3 YEAR OLD LANGUAGE
We have 9 out of 10 keys
We have KEYS
There you go understand NOW?

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo