The above video goes away if you are a member and logged in, so log in now!
Tested on a banned console?
Originally Posted by zylor
Tried it, doesn't work for a banned console at least. Fixed all the errors but still getting account is banned.
Last edited by boyadha; 02-24-2011 at 12:16 PM.
Did you try with a unused PSN account created on a PC?
Yup tested with a fresh psn account created an hour ago. I'm curious does PSN also access the 24.cer file as well? Or F***PSN forces it to access 27.cer only.
Originally Posted by arokh
If PSN does make use of 24.cer as well, i think we need a patched one that's compatible for this version of f***PSN as well. I'm guessing it's that cert that's sending other over the actual consoleid.
Correct me if i'm wrong guys.
P.S nice work in getting hiding consoleid integrated with f***PSN.
arokh, please specify which certificate to substitute on ps3 with this version.
Is it based on f***PSN 0.5 so that we have to substitute CA27?
Did some further testing, don't think it's any relation to 24.cer problem.
Either we overlooked some areas in hiding consoleid or PSN is using other IDs that's locked to a specific system to crosscheck bans.
For example, look at the attachment. Found this in another thread.
I believe it's based on f***PSN 0.5 thus ca27.cer from drizzt is to be used .
Originally Posted by oldhouse
arokh, might wanna doublecheck that the integration of hiding consoleid is 100%. Because i just tested hiding consoleid with charles + PS3DNS-GUI, it gave me a 8002a224 error, which i'm guessing is specifically addressing an invalid consoleid against their whitelist (on PSN's side).
Shouldn't your version of f***PSN should also give that error?
Tried it and still getting the banned code, even spoofed to 3.56
Source? If that's all true, then where are this data? We could have seen them through the packet sniffing
Originally Posted by boyadha
Can't handle more cheese