• Official PS3 Toolset is now supporting 4.92 Firmware

    View Official Release Post for additional information HERE

PS3 [Update: SSL issue Resolved} BG Toolset SSL Issues (80710A06 Error) (July 2024)

I did a client ssl support check

It supports these ciphers
TLS RSA WITH_AES_256_CBC_SHA256
TLS RSA WITH AES 128 CBC SHA256
TLS_RSA WITH_AES_256_CBC_SHA
TLS RSA WITH AES 128 CBC SHA
TLS RSA WITH_3DES_EDE_CBC_SHA
TLS_RSA WITH_RC4_128_SHA
TLS RSA WITH RC4 128 MDS
TLS_EMPTY_RENEGOTIATION_INFO_SCSV

You should not use these as they are known vulnerable
TLS RSA WITH 3DES EDE CBC SHA
TLS RSA WITH RC4 128 MD5
TLS_RSA WITH_RC4_128_SHA

I don't know if you are looking for a new cdn that supports PS3 client compliant certs but I did verify that Bunny.net a CDN I currently use served a TLSv1.2 (TLS_RSA_WITH_AES_128_CBC_SHA256) cert to my PS3.

At ZeroSSL they issue certificates with SHA-384 signature algorithm by default so that won't work.
 
TLS observatory result said domain ps3toolset.com has 2 ssl issuer: WE1 and R10.

*.ps3toolset.com is WE1 only accept ECDSA
www.ps3toolset.com is R10 it can accept RSA

Maybe the configuration is not properly configured. Can you please cross check this information ?
 
What I noticed, when checking the page with chrome, it does not force www.

Try open chrome on a desktop pc, press f12 to open dev tools, goto network tab, visit the url:

I can not post links: h....w... bg...

You will get a 200 success response for log.php, fires 2 post requests to two other php files with success.

Now open another tab open dev tools and visit the website without www:

I can not post links: h.......bg

You will experience the same behaviour when using mitmproxy, which obviously does not force www, even if you inspect the flow.request.url or flow.request.host in python.
This maybe a bug in mitmproxy.
The log.php response is 401 access denied.
Also there is a noticable layout shift when using without www.

A possible solution to make proxy work maybe to force www.
 
What I noticed, when checking the page with chrome, it does not force www.

Try open chrome on a desktop pc, press f12 to open dev tools, goto network tab, visit the url:

I can not post links: h....w... bg...

You will get a 200 success response for log.php, fires 2 post requests to two other php files with success.

Now open another tab open dev tools and visit the website without www:

I can not post links: h.......bg

You will experience the same behaviour when using mitmproxy, which obviously does not force www, even if you inspect the flow.request.url or flow.request.host in python.
This maybe a bug in mitmproxy.
The log.php response is 401 access denied.
Also there is a noticable layout shift when using without www.

A possible solution to make proxy work maybe to force www.
How do I set this up I'm at my desk right now can you walk me through the setup to force www. On mitmproxy so I can run it as the guinea pig
 
TLS observatory result said domain ps3toolset.com has 2 ssl issuer: WE1 and R10.

*.ps3toolset.com is WE1 only accept ECDSA
www.ps3toolset.com is R10 it can accept RSA

Maybe the configuration is not properly configured. Can you please cross check this information ?

Normally 1 ssl cert is enough, EDCSA is stronger than RSA, but PS3 does not comply with EDCSA thats why it need help from mitmproxy to act as a bridge to communicate to EDCSA server

is it possible to remove/disable WE1 cert for *.ps3toolset.com and just using R10 from Let's Crypt ?
 
Following cikocet guide on mitmproxy in the other thread, the SSL error is skipped but results in another 80710028 (CELL_HTTP_ERROR_CANNOT_AUTHENTICATE) error 401 with Acces denied when requesting the file log.php.

Following HWNJ comment in this thread, I would say, the error happens cause ps3toolset.com uses Cloudflare. Cloudflare supports HTTP/3 which is using UDP with default port 443 for the sites they serve. Since we don't redirect UDP port 443 and since mitmproxy would be unable to deal with this traffic anyway it bypasses the interception.

I didn't have the time yet to test, but following mitmproxy docs using-a-custom-server-certificate we should be able to generate a custom cert with openssl and disable http3 which is enabled by default. Then start mitmproxy with options:


mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem


This should let the ps3 browser fall back to HTTP/2, which mitmproxy should be able to catch.

(Sorry I can't post any links, because this is my first reply)

Error 80710028 could also be related to flash player, since mitmproxy does not send application/x-shockwave-flash header.
Can u do a toutorial on it bc idont know where to write mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem
 
Can u do a toutorial on it bc idont know where to write mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem
Bash terminal on Linux, CMD on Windows.
This is a console app, it has no fancy GUI and you need at least some basic understanding on how to operate a computer from the command line.
 
Bash terminal on Linux, CMD on Windows.
This is a console app, it has no fancy GUI and you need at least some basic understanding on how to operate a computer from the command line.
It says certificate file does not exist : cert.pem
 
Following cikocet guide on mitmproxy in the other thread, the SSL error is skipped but results in another 80710028 (CELL_HTTP_ERROR_CANNOT_AUTHENTICATE) error 401 with Acces denied when requesting the file log.php.

Following HWNJ comment in this thread, I would say, the error happens cause ps3toolset.com uses Cloudflare. Cloudflare supports HTTP/3 which is using UDP with default port 443 for the sites they serve. Since we don't redirect UDP port 443 and since mitmproxy would be unable to deal with this traffic anyway it bypasses the interception.

I didn't have the time yet to test, but following mitmproxy docs using-a-custom-server-certificate we should be able to generate a custom cert with openssl and disable http3 which is enabled by default. Then start mitmproxy with options:


mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem


This should let the ps3 browser fall back to HTTP/2, which mitmproxy should be able to catch.

(Sorry I can't post any links, because this is my first reply)

Error 80710028 could also be related to flash player, since mitmproxy does not send application/x-shockwave-flash header.

Tested this real quick with http3 disabled, then with http3 and http2 disabled, same behavior.

Bash terminal on Linux, CMD on Windows.
This is a console app, it has no fancy GUI and you need at least some basic understanding on how to operate a computer from the command line.
`mitmweb` gives you a webui

Following cikocet guide on mitmproxy in the other thread, the SSL error is skipped but results in another 80710028 (CELL_HTTP_ERROR_CANNOT_AUTHENTICATE) error 401 with Acces denied when requesting the file log.php.

Following HWNJ comment in this thread, I would say, the error happens cause ps3toolset.com uses Cloudflare. Cloudflare supports HTTP/3 which is using UDP with default port 443 for the sites they serve. Since we don't redirect UDP port 443 and since mitmproxy would be unable to deal with this traffic anyway it bypasses the interception.

I didn't have the time yet to test, but following mitmproxy docs using-a-custom-server-certificate we should be able to generate a custom cert with openssl and disable http3 which is enabled by default. Then start mitmproxy with options:


mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem


This should let the ps3 browser fall back to HTTP/2, which mitmproxy should be able to catch.

(Sorry I can't post any links, because this is my first reply)

Error 80710028 could also be related to flash player, since mitmproxy does not send application/x-shockwave-flash header.

Why use a custom cert? I generated one as documented, but it doesn't seem to be different in any important way(other than having my name on it)
 
Last edited by a moderator:
Tested this real quick with http3 disabled, then with http3 and http2 disabled, same behavior.


`mitmweb` gives you a webui



Why use a custom cert? I generated one as documented, but it doesn't seem to be different in any important way(other than having my name on it)
Does it work though and how do i generate one. ?
 
For the .php files Access Denied / 401. Maybe because the php server configuration not using cert file/key from Let's Crypt / R10 ?
 
Hello.

We are aware of the SSL problem currently on ps3toolset.com.

via bguerville:

The Cloudflare SSL certificate provider upgraded their certs to ECDSA, they're no longer PS3 compliant. I just tried to install a let's encrypt certificate, it uses RSA sha256 as required, it's signed with a certificate authority included in CA_LIST.cer since fw 4.86 but it won't load. I may have found a potential solution with Cloudflare but it's 10 bucks a month.

All we need is a certificate that's guaranteed to work on PS3, the best would be to find a SSL certificate reseller that allows you to access a test page for each certificate they sell so we can choose something that works.

If anyone is savvy with SSL and hosting, or if they know a solution or a reseller where we can have test pages, that would be helpful. Pricing should be anywhere between USD 50 and 150 per year depending, I think.

So, in short, if there is anyone out there who has a solution, or knows of a reseller that can be used for this, please PM me with details or post them here in this thread.


If anyone would like to donate using PayPal, please use the following address [email protected]

Thank you for your understanding and patience while we get this sorted out.
so there's no fix to this yet? because all im wanting to do is jailbreak my ps3 but i do understand and will be patient
 
Got it working!
The 401 issue is because for some unknown reason beyond my comprehension, if the client does not support GZIP or Deflate encoding, the server fails to set a session cookie on the first request. Requests to subpages (file.php, log.php, etc.) then fail because the cookie is missing. I will post a proper working guide in a separate thread for better visibility.
 
Got it working!
The 401 issue is because for some unknown reason beyond my comprehension, if the client does not support GZIP or Deflate encoding, the server fails to set a session cookie on the first request. Requests to subpages (file.php, log.php, etc.) then fail because the cookie is missing. I will post a proper working guide in a separate thread for better visibility.
you fixed the website?
 
Got it working!
The 401 issue is because for some unknown reason beyond my comprehension, if the client does not support GZIP or Deflate encoding, the server fails to set a session cookie on the first request. Requests to subpages (file.php, log.php, etc.) then fail because the cookie is missing. I will post a proper working guide in a separate thread for better visibility.

@NiQ you got the ps3toolset to work? Which guide did you follow?
 
Got it working!
The 401 issue is because for some unknown reason beyond my comprehension, if the client does not support GZIP or Deflate encoding, the server fails to set a session cookie on the first request. Requests to subpages (file.php, log.php, etc.) then fail because the cookie is missing. I will post a proper working guide in a separate thread for better visibility.

You're about to be the hero of the quarter once you post that thread.
 
I kept the Flash Backup dump.bin
Is it possible for me to use a different flasher to flash the dump.bin file back onto the NOR/NAND memory of my PS3?
 
Back
Top