Naima PS3 CFW v3.55 / 3.60 Hybrid PSN Ready Custom Firmware

114w ago - Just under a month ago Naima released PS3 Custom Firmware 3.55, and today he has updated it to Naima PS3 CFW v3.55 / 3.60 Hybrid which is PSN ready Custom Firmware!

Downloads: Naima PS3 CFW v3.55 / 3.60 Hybrid PSN Ready Custom Firmware (Patch.diff) / Naima PS3 CFW v3.55 / 3.60 Hybrid PSN Ready Custom Firmware (Patch.diff) (Mirror) / Naima PS3 CFW v3.55 / 3.60 Hybrid PSN Ready Custom Firmware (Full) / PS3 3.55-60 CFW Naima Modbyivangelillo App_Home v3 / Charles Proxy SSL Proxying Certificate

From Logic-Sunrise, roughly translated: Remember, Naima was the first to have released a custom firmware (cfw) to directly connect to PSN or via Charles FckPSN.

Although since the ITA allow CFW to connect to the network without special configuration and especially without a computer, Naima back on center stage. Indeed, always starting the same basis as the cfw Kmeaw, Naima leaves a second CFW.

The big news is the addition of files from the official firmware 3.60. In addition, a file CA27.cer FckPSN modified to Charles and is already included. In the characteristics of this CFW, Naima has included the necessary but not least sufficient to ensure stability:

• Support for Peek / Poke Fluke
  
• Added "Install Package Files"
  
• Support Pkg signed or unsigned
  
• Replacement of certificate CA27.cer
  
• Maximum stability and cleanliness in all the changes.
  

Naima chose to replace the 27 certificate because it is obsolete. He further reported that the certificate 24 was used by some games. Replace the certificate 24 could therefore have undesirable side effects. In addition, you will notice that he has chosen to delete app_home/PS3_Game for security measures, saying that playing without disc is more risky for online play.

Coment install cfw:

• Beginnings official firmware is ideal,
  
• Check the integrity of the original PS3UPDAT.PUP, it should be:
  

MD5: CA595AD9F3AF8F1491D9C9B6921A8C61
SHA1: a3a0d1c61e17c6a58a5fa247a3dbb51524329e0a

Check the integrity of the "PS3UPDAT.PUP custom", it should be:

MD5: 2C608AA99772E625BF708908AB6AF9DF
SHA1: c9db35a8d45c7d5286d581e87bb647ae4aa1e1b7

Perform the installation from the Recovery Mode. Warning, the archive contains only the patch. There is of course an OFW patch 3.55. A second archive with patched OFWs arrive in the day.

From Naima's initial post on Elotrolado (roughly translated):

Well, I present what will be possibly my last contribution to the scene of PS3. The reasons I'll explain later.

What is this CFW?
A hybrid 3.55, 3.60 includes some files, but to all intents and purposes acts as a 3.55

What features do you have?
The minimum necessary in order to provide stability.
- Support for Peek / Poke through patching lv1, lv2_kernel (Thanks to Flukes)
- Add 'Install Package Files' by modifying category_game.xml
- Installing. Pkg unsigned and signed by pseudo-nas_plugin.sprx patching (the only method that does not mean Sony reveal key)
- Modification of vsh.self and including index.dat, original version.txt 3.60, internal version is for 3.60 CFW
- Replacement of CA27.cer CA certificate by including in the implementation Charles Web Debugging Proxy
- Maximum stability and cleanliness in all modifications.

CA27 is included for various reasons:
- Allow research on communication protocols used by PS3 by MITM
- Allow changes on the fly, strengthened by example.

Why replace rather than add and why we chose the 27?
- Because it is not known if they add, and we chose the 27 because the license is included in the PS3 is outdated and therefore no longer valid. The 24 is also expired and was replacing the first, but was found later that it was used by a game, it was impossible to know this fact a priori. Replace an expired certificate is not therefore valid, would imply unwanted side effects.

Why replace it by including Charles?
Because any CA certificate which has the private key we serve, one that we generate for example, but since you are using the application for the MITM attack and certificate is as good as any other, we choose the same.

I also include the certificate attached to the post of Charles with the private key, any developer can use it without creating another.

Research on the content of the CFW, lv1 files, lv2_kernel, category_game.xml, nas_plugin.sprx, vsh.self are different from those known so far used in other CFW, why?
For the simple reason that he 'changed' me and not exactly the same, the encryption also increases the differences. But the functionality is the same as the patches.

Why not include the link in the XMB to app_home?
- For safety, say you play without disc inside is more 'risky' ivangelillo has made ​​a mod of the CFW with the link for those with damaged reader.

Installation is safe?
100% sure there is nothing, not even an official firmware upgrade. It is as safe as it can be an OFW or CFW of kmeaw. Of course, I take responsibility for any accidents that may occur.

How I can avoid risks?
- Start from a OFW is ideal.
- Check the integrity of the original PS3UPDAT.PUP, it should be: = CA595AD9F3AF8F1491D9C9B6921A8C61 MD5, SHA1 = a3a0d1c61e17c6a58a5fa247a3dbb51524329e0a
- Check the integrity of the 'Custom PS3UPDAT.PUP', it should be: = 2C608AA99772E625BF708908AB6AF9DF MD5, SHA1 = c9db35a8d45c7d5286d581e87bb647ae4aa1e1b7

So what I need with this CFW for connecting to PSN?
- Currently the CFW does not alter the version number of face-to PSN, we can connect only because Sony has left the door open for 3.55!

Why do you say that this is possibly your last contribution to the 'scene' for PS3?
- Several reasons but the main one is that the oven is too hot to make buns, especially from the police show house Graf_Chokolo

Moreover, the PS3 hacks is something that interests me only as a curiosity and personal challenge, otherwise I give a damn and given the legal situation not going to keep putting a target on his chest to shoot Sony.

Can anyone continue your work?
- Maintaining the credit, of course. Always keep it running 'the invention' I imagine Sony will soon show their cards.

Include post attached to the certificate used in. P12. Pem, password 1234 and private key independently, without encryption. Regards.

Utilities:

• Bsdiff: http://sites.inka.de/tesla/download/bsdiff4.3-win32.zip
  
• md5: http://www.fourmilab.ch/md5/md5.zip
  
• sha1: http://www.hashcash.org/binaries/win32/sha1.exe