PS3 PlayStation 3 Firmware Update 4.70 Now Live

Sony has released official firmware update v4.70 and as expected this is a minor update, However, Sony does this time around have a few features they would to tell you about in regards to Closed Caption Features on BluRay and DVD disc. See the details in the change-log notes provided [break]s[/break] below:

UPDATE: Checkout all the 4.70 Related Updates and releases of CFW / Homebrew via this link

​

​

Official Firmware v4.70 Changes:

• Closed Captions are now supported for the Playback of Blu-Ray Disc titles and DVDs. To display closed captions, select [Settings] > [Video Settings] > [Closed Captions].
• The style used for for closed captions, such as the font, size and color, can now be adjusted. Select [Settings] > [Video Settings] > [Closed Captions Settings].
  
• The name and icon for
  
  (PSN℠) have been changed to
  
  (PlayStation™Network).
  
• UPDATE: IDPS Stealer has been patch in 4.70

​

Source: gearnuke.com/ / dualshockers.com

---

Checkout all the Official Firmware Changelogs for the PlayStation 3 via this link
​

 

Well some people called it and here it is. Now lets see if the 4.66 spoofer can be adjusted for this update.

 

it seems to be mandatory

 

Haaaa, now we will see exactly what Sony is trying to do.
But it was logical that an update comes after the blocking of spoofs.

 

4.70 spoof works

 

4.70 spoof works

What 4.70 spoof? I'm at work and should be coding but every time a dev comments here I get distracted. :bangdesk:

 

4.70 spoof works

Looking into recent psn server changes, 4.66 seems to support both the previous and the new handshake protocols.
I suspect 4.70 will just support the new one.
If this comes to be true, Sonia can easily detect a spoofed 4.65 trying to connect to PSN ...
This makes me think there is a considerable ban risk when using a 4.66 to 4.70 spoofer.
(deep testing is needed)

 

Looking into recent psn server changes, 4.66 seems to support both the previous and the new handshake protocols.
I suspect 4.70 will just support the new one.
If this comes to be true, Sonia can easily detect a spoofed 4.65 trying to connect to PSN ...
This makes me think there is a considerable ban risk when using a 4.66 to 4.70 spoofer.
(deep testing is needed)

Always there is a ban risk when using cfw, and this has never been a problem to those cheaters with older DEX FW. (for ex : DEX 4.46 / 4.50 / 4.55 users)

 

4.66 change SSL thing not because spoof's but because "Poodle" problem. But now they figure out that gave them extra feature.. Locking spoofs. And yes, 4.70 will use only new handshake imo. All spoofs from 4.66 fw to actual should work for now.

Maybe this can help somehow spoof makers: POODLE - Wikipedia, the free encyclopedia
You can read more about poodle, then maybe you find how changes was made.

Edit: Here is also test for poodle: https://www.poodletest.com/
PROBABLY if your spoofed ps3 test show you vunerable. Moment when you get not vunerable PROBALBY give you also access to PSN.

One more edit: Sony can really easy check that you have spoof under 4.66. Is simple for them like poodle test above. Is good to wait for proper spoof or go to 4.66+ cfw for PSN users. Ban risk increased for x.xx-4.65 for now.

Last edit (I swear):

Looking into recent psn server changes, 4.66 seems to support both the previous and the new handshake protocols.
I suspect 4.70 will just support the new one.
If this comes to be true, Sonia can easily detect a spoofed 4.65 trying to connect to PSN ...
This makes me think there is a considerable ban risk when using a 4.66 to 4.70 spoofer.
(deep testing is needed)

[MENTION=124]kokotonix[/MENTION] you wrong, that not 4.66 suport both handshakes. Sony server suport both of them and now turn off old one. 4,66 suport only new handshake. That explain why old spoofed cfw can get to psn until changes on server.

 

[MENTION=124]kokotonix[/MENTION] you wrong, that not 4.66 suport both handshakes. Sony server suport both of them and now turn off old one. 4,66 suport only new handshake. That explain why old spoofed cfw can get to psn until changes on server.

Yeah. You could be right.
Or 4.66 supported both, and when one fails it tries the other.
Anyway
I have a working spoofer ready , but I'm not sure if it is a good idea to release it, for the reasons stated earlier today.
IMHO It will probably be better to just wait for 4.70 CFW...

 

I have a working spoofer ready , but I'm not sure if it is a good idea to release it, for the reasons stated earlier today.
IMHO It will probably be better to just wait for 4.70 CFW...

Does it fully support REBUG 4.65.2 also?

 

also note there seems to be 8 new certs ...

 

also note there seems to be 8 new certs ...

MD5 2/24/2015

\dev_flash\data\cert\
4920b847039f341361e8db66214f913e CA58.cer 1.2 KB (1,261)
72a3669e936fa6ca128b12fa6d2602ee CA51.cer 1.5 KB (1,533)
2e0cf9fd6ff9126b1fbf0290901f0ad4 CA52.cer 1.7 KB (1,700)
1e8af9a33f6e16fa41e03feb1412ab84 CA53.cer 1.3 KB (1,367)
afa7c51b1be82699985b1cf2f6552663 CA55.cer 1.4 KB (1,424)
59ded95ba90cc18fc757e2d9045b58f6 CA54.cer 1.4 KB (1,399)
024c047c146cad9c7b189e78a0599dcc CA56.cer 2.6 KB (2,671)
e1fb41d30fb450ce6c86ea15627cb6f2 CA57.cer 1.9 KB (1,927)

TOTAL: 8 files - 13.0 KB (13,282 bytes)

Yes 8 more but it is useless to add these certificates to pre 4.66 fw unless it's using 4.70 vsh, because those older vsh do not load these certificates.

 

The spoofers may not forget to add those new 8 certs.
And, about cobra, it is always good to remember: that the vsh.self stage2 hashes must be updated.

 

Yeah. You could be right.
Or 4.66 supported both, and when one fails it tries the other.
Anyway
I have a working spoofer ready , but I'm not sure if it is a good idea to release it, for the reasons stated earlier today.
IMHO It will probably be better to just wait for 4.70 CFW...

Is it working on 4.65 D-REX ? Or just from 4.66 onwards

 

MD5 2/24/2015

\dev_flash\data\cert\
4920b847039f341361e8db66214f913e CA58.cer 1.2 KB (1,261)
72a3669e936fa6ca128b12fa6d2602ee CA51.cer 1.5 KB (1,533)
2e0cf9fd6ff9126b1fbf0290901f0ad4 CA52.cer 1.7 KB (1,700)
1e8af9a33f6e16fa41e03feb1412ab84 CA53.cer 1.3 KB (1,367)
afa7c51b1be82699985b1cf2f6552663 CA55.cer 1.4 KB (1,424)
59ded95ba90cc18fc757e2d9045b58f6 CA54.cer 1.4 KB (1,399)
024c047c146cad9c7b189e78a0599dcc CA56.cer 2.6 KB (2,671)
e1fb41d30fb450ce6c86ea15627cb6f2 CA57.cer 1.9 KB (1,927)

TOTAL: 8 files - 13.0 KB (13,282 bytes)

Yes 8 more but it is useless to add these certificates to pre 4.66 fw unless it's using 4.70 vsh, because those older vsh do not load these certificates.

Yes. you're right - I've just seen that almost at the same time you've published

We must find 8 old certs not used anymore and replace the filenames to point to the new certs in VSH, or the version spoofer may not work - or will be a even higher BAN risk
I was going to release a psnpatch spoofer to 4.70, but with this, it will be delayed until further investigation.

Or wait for 4.70 CFW.
Yes. That's the wiser approach.

 

I'll see if later today, I can carry on some tests on FERROX 4.70/DualBoot and start porting on COBRA LITE.
If aldo is able to release a test version of the new IrisMAN with payloads 4.70, it would be a good opportunity to try.

 

I'll see if later today, I can carry on some tests on FERROX 4.70/DualBoot and start porting on COBRA LITE.
If aldo is able to release a test version of the new IrisMAN with payloads 4.70, it would be a good opportunity to try.

Once you released your 4.70 DB, I'll test and use your CoreOS as PS3 Dump Checker embeded noFSM patch.

 

Once you released your 4.70 DB, I'll test and use your CoreOS as PS3 Dump Checker embeded noFSM patch.

See if I can release it in the coming hours.
Multiman 4.66.10 work properly on FERROX 4.70, but no supporting firmware
PSNPATCH (latest version) works correctly was FERROX 4.70

We are testing IRISMAN v3.43....

 

I'm currently trying to do a spoofer for 4.66 and 4.65 systems, however these freaking 8 new certificates are annoying me.
I spoofed to 4.70 successfully, however my PS3 tells me the error code 80710101 (no internet connection) when trying to get into PSN, I guess this has to do with the certs. Did anyone found out already if 8 other certificates aren't used anymore and if so which?