[Rumors] Sắp có CFW 4.00 chơi game ko cần USB hack, ko đĩa mồi

zZigxZagz · 16/1/12

mromega nói: ↑

The f*ck is that? có hack hả bác, hay bác chờ FF13-2
Click to expand...

hắc hắc hắc hắc hắc. xin lỗi mình bị lên cơn hen suyễn

maxxxpham · 19/1/12

TIN MỚI FW 4.0: Status Update on PS3 4.0 Homebrew Enabler (HEN) by KaKaRoTo

Today PlayStation 3 hacker KaKaRoToKS has posted a status update on the PS3 4.0 Homebrew Enabler (HEN), which comes just six weeks since the previous confirmation that it indeed works on Sony's latest Firmware version.

To quote: Here’s a “quick” status update on the 4.00 HEN (Homebrew ENabler) for PS3.

Following my clarifications from almost 2 months ago here, there has been a lot of progress. We have not been slacking off, we’re a group of about 10 developers working together for the last 2 months, for sometimes 15 hours everyday in order to bring back homebrew support to the latest version of the PS3.

There are three major parts to the HEN, first, getting the packages to install on the PS3, that part is done, completed, tested, debugged, etc.. the second part is to get the apps to run, that one still has major issues... the last part is something I will not discuss for now (it’s a surprise) but it’s about 60% to 70% done (and it has nothing to do with peek&poke and has nothing to do with backup managers or anything like that. This is and will stay a piracy-free solution for the PS3).

Now, running apps is the biggest challenge that we’ve been working on for the past 2 months. As some of you know, if you’ve been following me on Twitter, we originally had hoped for Mathieulh to give us the “NPDRM hash algorithm” that was necessary to run the apps, but he was reluctant, he kept doing his usual whore so people would kiss his feet (or something else) so he’d feel good about himself. But in the end, he said that he refuses to give us the needed “NPDRM hash algorithm” to make it work... So what I initially thought would be “this will be released next week” ended up taking a lot more time than expected, and we’re still nowhere near ready to make it work.

Mathieulh kept tossing his usual “riddles” which he thinks are “very helpful for those who have a brain”, and which pisses off anyone who actually does... so he told us that the solution to all our problems was to look in appldr of the 3.56 firmware.. and that it was something lv1 was sending appldr which made the “hash check” verified or not… so we spent one month and a lot of sweat and after killing a few of our brain cells out of exhaustion, we finally concluded that it was all bullsht. After one month of reading assembly code and checking and double-checking our results, we finally were able to confirm that that hash algorithm was NOT in the 3.56 firmware like he told us (at all).

He said that it was an AES OMAC hash, but after tracking all the uses of the OMAC functions in appldr, we found that it was not used for the “hash”… he then said “oh, I meant HMAC”, so we do that again and again come up with the same conclusion, then we’re sure it’s not in appldr, and then he says “ah no, it’s in lv1”.. have a look for yourself to what he decided to write: ps3devwiki.com/index.php?title=Talk:KaKaRoTo_Kind_of_%C2%B4Jailbreak%C2%B4

That happened after the huge twitter fight I had with him for being his usual arrogant self and claiming that he “shared” something (For your information, the code that he shared was not his own, I have proof of that too (can’t show you the proof because even if I don’t respect him, I gave him my word to not share what he gave me, and I respect my word) since he forgot to remove the name of the original developer from one of the files... also it was completely useless and was not used at all, just made me waste a day reading the crappy undocumented code. So why is he still trying to force his “advice” through these riddles even after we had that fight? Well to sabotage us and make us lose all those months of hard work!

So anyways, we had all accepted that Mathieulh was full of sht (we knew before, but we gave him the benefit of the doubt) and decided to continue working without considering any of his useless riddles. So we then tried to exploit/decrypt the 3.60+ firmware in order to get the algorithm from there.

Now, a few more weeks later, we finally have succeeded in fully understanding that missing piece from the “NPDRM hash algorithm”, and here it is for everyone’s pleasure with some prerequisite explanation:

A game on the PS3 is an executable file in a format called a “SELF“file (kind of like .exe on windows), those “self” files are cryptographically signed and encrypted.. For PSN games (games that do not run from a Blu-ray disc), they need to have an additional security layer called “NPDRM”. So a “NPDRM self” is basically an executable that is encrypted and signed, then re-encrypted again with some additional information. On 3.55 and lower, we were able to encrypt and sign our own self files so they would look like original (made by sony) “NPDRM self” files, and the PS3 would run them without problem.

However, it wasn’t really like an original file.. a real NPDRM self file had some additional information that the PS3 simply ignored, it did not check for that information, so we could put anything in it, and it worked. Since the 3.60 version, the PS3 now also validates this additional information, so it can now differentiate between NPDRM self files created by Sony and the ones that we create ourselves for homebrew. That’s the “NPDRM hash algorithm” that we have been trying to figure out, because once we can duplicate that information in the proper manner, then the PS3 will again think that those files are authentic and will let us play them.

Another important point to explain, I said a few times that the files are “signed”.. this means that there is an “ECDSA signature” in the file which the PS3 can verify. The ECDSA signature is something that allows the PS3 to verify if the file has been modified or not.. it is easy to validate the signature, but impossible to create one without having access to the “private keys” (think of it like a real signature, you can see your dad’s signature and recognize it, but you can’t sign it exactly like him, and you can recognize if your brother tried to forge his signature). So how were we able to sign the self files that were properly authenticated on 3.55?

That’s because this “ECDSA signature” is just a very complicated mathematical equation (my head still hurts trying to fully understand it, but I might blog about it in the future and try to explain it in simple terms if people are interested), and one very important part of this mathematical equation is that you need to use a random number to generate the signature, but Sony had failed and used the same number every time.. by doing that, it was easy to just find the private key (which allows us to forge perfectly the signature) by doing some mathematical equation on it. So to summarize, a “signed file” is a file which is digitally signed with an “ECDSA signature” that cannot be forged, unless you have the “private key” for it, which is impossible to obtain usually, but we were able to obtain it because Sony failed in implementing it properly.

Now, back on topic.. so what is this missing “NPDRM hash algorithm” that we need? well it turns out that the “NPDRM self” has a second signature, so it’s a “encrypted and signed self file” with an additional layer of security (the NPDRM layer) which re-encrypts it and re-signs it again. That second signature was not verified in 3.55 and is now verified since the 3.60 version of the PS3 firmware.

One important thing to note is that Sony did NOT make the same mistake with this signature, they always used a random number, so it it technically impossible to figure out the private key for it. To be more exact, this is the exact same case as the .pkg packages you install on the PS3, you need to patch the firmware (making it CFW) so that those .pkg files can be installed, and that’s because the .pkg files are signed with an ECDSA signature for which no one was able to get the private key. That’s why we call them “pseudo-retail packages” or “unsigned packages”.

The signature on the NPDRM self file uses the exact same ECDSA curve and the same key as the one used in PS3 .pkg files, so no one has (or could have) the private key for it. What this means is that, even though we finally figured out the missing piece and we now know how the NPDRM self is built, we simply cannot duplicate it.

The reason we wasted 2 months on this is because Mathieulh lied by saying that he can do it.. remember when the 4.0 was out and I said “I can confirm that my method still works” then he also confirmed that his “NPDRM hash algorithm” still works too? well he didn’t do anything to confirm, he just lied about it because there is no way that he could have verified it because he doesn’t have the private key.

I said I will provide proof of the lies that Mathieulh gave us, so here they are: he said it’s in 3.56, that was a lie, he said it’s an AES OMAC, that was a lie, he said it’s an HMAC, that was a lie, he said it’s in appldr, that was a lie, he said it’s in lv1, that was a lie, he said that he can do it, that was a lie, he said that “it takes one hour to figure it out if you have a brain”, that was a lie, he said that he verified it to work on 4.0, that was a lie, he said that he had the algorithm/keys, that was a lie, he said that once we know the algorithm used, we can reproduce it, that was a lie, he kept referring to it as “the hash”, that was wrong.

The proof ? It’s an ECDSA signature, it’s not a hash (two very different terms for different things), it was verified by vsh.self, it was not in lv2, or lv1, or appldr, and the private key is unaccessible, so there is no way he could build his own NPDRM self files. Now you know the real reason why he refused to “share” what he had.. it’s because he didn’t have it...

So why do all this? was it because his arrogance didn’t allow him to admit not knowing something? or was it because he wanted to make us lose all this time? To me, it looks like pure sabotage, it was misleading information to steer us away from the real part of the code that holds the solution... That is of course, if we are kind enough to assume that he knew what/where it was in the first place. In the end, he wasn’t smart enough to only lie about things that we could not verify.. now we know (we always knew, but now we have proof to back it) that he’s a liar, and I do not think that anyone will believe his lies anymore.

Enough talking about liars and drama queens, back to the 4.0 HEN solution... so what next? well, we now know that we can’t sign the file, so we can’t run our apps on 3.60+ (it can work on 3.56 though). What we will do is look for a different way, a completely new exploit that would allow the files we install to actual run on the PS3. We will also be looking for possible “signature collisions” and for that we will need the help of the community, hopefully there is a collision (same random number used twice) which will allow us to calculate the private key, and if that happens, then we can move forward with a release.

When will the “jailbreak” be released? If I knew, I’d tell you, but I don’t know.. I would have said in last November, then December, then before Christmas, then before new year, etc... but as you can see, it’s impossible to predict what we will find.. we might get lucky and have it ready in a couple of days, or we may not and it will not be ready for another couple of months.. so all you need to do is : BE PATIENT (and please stop asking me about an estimated release date)!

I would like to thank the team who helped on this task for all this time and who never got discouraged, and I’d like to thank an anonymous contributor who recently joined us and who was instrumental in figuring it all out. We all believe that freedom starts with knowledge, and that knowledge should be open and available to all, that is why we are sharing this information with the world. We got the confirmation (by finding the public key used and verifying the signatures) yesterday and since sharing this information will not help Sony in any way to block our efforts in a future release, we have decided to share it with you. We believe in transparency, we believe in openness, we believe in a free world, and we want you to be part of it.

If you want to know more about this ECDSA signature algorithm, read this interesting paper (engineering.purdue.edu/kak/compsec/NewLectures/Lecture14.pdf) that explains it in detail, and you can also watch Team Fail0verflow’s CCC presentation (youtube.com/watch?v=5E0DkoQjCmI) that first explained Sony’s mistake in their implementation, which made custom firmwares possible.

Thanks for reading,

KaKaRoTo
Click to expand...

babylove243b · 19/1/12

tin này hot nè, tối về xem thử =]

duoq · 19/1/12

Tóm tắt sơ cho những ai không hiểu tiếng Anh:
- Đầu tiên Kakalot ủa lộn Kakaroto cho biết anh và các cộng sự vẫn đang nỗ lực ngày đêm nghiên cứu về fw mới của PS3.
- Đáng tiếc, vì Kaka và các cộng sự nghe lời của Matthieu, rằng tên này đang nắm trong tay "NPDRM hash algorithm” mà ta có thể hiểu là key, nhưng tên Matt này không cho, cứ nhử nhử rằng "không phải cái này, cũng không phải cái kia" nên làm cả nhóm chạy lòng vòng mất thời gian mày mò vô ích. Cuối cùng Kaka cũng hiểu ra, làm đếch gì có cái gọi là "NPDRM hash algorithm", cho nên khi dân chúng đòi Matt tung ra thì hắn làm gì có mà tung.
- Còn về việc "NPDRM hash algorithm", nhóm Kaka đang nỗ lực nhưng vẫn phải hi vọng vào vận may. Signature (chữ kí) dùng để xác định game này còn zin hay không và 1 game fw mới muốn chơi được thì game đó phải được "kí" (sighed), mà chữ kí do PS3 fw 3.6+ tạo ra là random. Do đó họ cần 1 signature collision (chữ kí xuất hiện 2 lần) để từ đó tìm ra nguyên tắc tính toán private key. Vì hên xui nên họ không thể nói trước ngày họ cho ra hack mới (jailbreak hoặc cfw).

Ít ra đọc cái này cũng mừng rằng vẫn còn hacker tận tâm với PS3. Còn thằng Matt thì đúng là 1 con troll siêu bự.

princetimmiz · 19/1/12

quả này con 4.00 có miếng hi vọng , vài tháng nữa k ra là lên i7 VGA khủng chơi gameeee

minhjirachi · 19/1/12

Nghe tin này coi bộ đã warm-up lên nhiều rồi. Thank a lot!

taituxdseller · 19/1/12

ai thí mạng trước đi

babylove243b · 19/1/12

taituxdseller nói: ↑

ai thí mạng trước đi
Click to expand...

có ra đâu mà thí mạng trước =]

mami9x · 20/1/12

tiep tuc doi den ngay` tan the' lun de may bo`

aaaaaaaaaaaaaaaa · 20/1/12

Có quá trời game PSN với bây giờ có thú vui tao nhã là chơi lại mấy game chưa chơi hay quá đỉnh của PS1 và PS2 mà lo gì thời gian chờ đợi. Rùi sẽ qua nhanh tới lúc có CFW 4.0 thôi mà mấy bồ ơi

haihieu003 · 20/1/12

trích bài KaKa - "so all you need to do is : BE PATIENT" cứ thế mà làm thôi :)
mua ps3 mấy tháng rồi mà nhiều game đỉnh chưa chơi hết, đang chiến Mass Effect 2 hay quá trời @.@

minhjirachi · 20/1/12

Nghe nói ổng sẽ đưa ra cái app cho tất cả mọi người để quét cái keys trong mỗi game rồi sau đó mình copy dòng đó đưa lại cho ổng. Ông Kaka cũng thông minh lém chứ bộ. Việc tưởng như khó nhưng nếu làm với sức lực của cả cộng động thì ... dễ như trở bàn tay. Nếu vậy thì 1 ngày sẽ kiểm tra được bao nhiêu game đây? Mình thì nghĩ chắc được cả ngàn key luôn (nếu xui ).

maxxxpham · 21/1/12

LẠi thÊm tin nỮa vỀ fw 4.0 ps3

adding 'install package files' on ps3 4.00 dev_flash mod
below is a video demonstrating my ps3 4.00 dev_flash modification, which simply allows users to install retail signed package (pkg) files from the playstation 3 xmb.

Note: This modification does not allow the installation / usage of unsigned content / ps3 homebrew etc. This is purely a convenience hack and is aimed for use by those who have hardware flashers which allow dual boot.

After technodon's work creating a modified kiosk dev_flash which lets you install retail signed package files. The restrictions of having to use kiosk firmware inspired me to find a way to add "install package files" for retail firmware.

This is hack does the following things:

Adds "★ install package files" and "★ /app_home/ps3_game/" to "game" on the xmb (allowing the user to install retail package files anytime they want)
adds other debug functions which are small but still there
does not give access to "★ debug setting" (reasons for this are explained below)

installation instructions:

This installation procedure is the similar to technodon's original dev_flash hdd swap procedure

for this you will need two hard drives a e3 flasher or similar device to downgrade your ps3 (assuming that you're on firmware 4.00 and you have an e3 flasher)

downgrade to 3.55 using the downgrade tools from e3 (of course when downgrading to 3.55 make sure you use a different hdd than the hdd which you were using 4.00)
once booted back into the xmb turn off the console
swap hard drives turn on the system, press the ps button and you will be asked to reinstall the firmware
place the pup file from the e3 downgrade tools in the normal ps3/update usb folder and follow the on-screen instructions to reinstall the firmware
then install dev_blind.pkg & blackb0x ftp from install packages
run dev_blind then blackb0x and ftp into the console
goto /dev_blind delete everything and replace them with the customised dev_flash
press the ps button and the console should reboot and and ask to reinstall the firmware again, switch off the console and swap the hard drive back
turn on the console press the ps button twice
the console should boot back into 3.55 rogero
goto system update and install 4.00 ofw
once installed turn the console off again and swap hard drives back and you should boot into a modified 4.00 retail firmware.

My package (downloadable at http://www.multiupload.com/20lfvkuhdg) includes:

My modded dev_flash
ofw 4.00 ps3updat.pup

sorry about the camera quality, it's the best i can manage.

P.s. Btw the "nas_plugin.sprx" in this dev_flash has not been altered to achieve "install package files". Also for those who will analyze my modded dev_flash, you will find that i have used debug .sprx files from the a debug 4.00 pup.

P.p.s. I originally intended to get "★ debug settings" to work with this. But usage of "debug settings" required the ps3 to use a debug vsh.self, and that crashes the ps3 when trying to load applications (i did some other things as well to prevent the ps3 from giving me a rsod when i swapped the vsh.self files, i'm not detailing it in public because i don't want sony to patch it)
Click to expand...

SienRyu · 21/1/12

Lôi mới game đỉnh chưa chơi trên ps3 ra chơi + psn!

Nói ko điêu chứ tà tà chơi đợi 1 năm sau ra cfw cũng được!

oOziczacOo · 21/1/12

SienRyu nói: ↑

Lôi mới game đỉnh chưa chơi trên ps3 ra chơi + psn!

Nói ko điêu chứ tà tà chơi đợi 1 năm sau ra cfw cũng được!
Click to expand...

Đâu phải game nào đỉnh cũng hợp khẩu vị của mình đâu trong khi game mới ra có mấy cái kết kinh khủng kìa >.< !!!

taituxdseller · 21/1/12

aaaaaaaaaaaaaaaa nói: ↑

Có quá trời game PSN với bây giờ có thú vui tao nhã là chơi lại mấy game chưa chơi hay quá đỉnh của PS1 và PS2 mà lo gì thời gian chờ đợi. Rùi sẽ qua nhanh tới lúc có CFW 4.0 thôi mà mấy bồ ơi
Click to expand...

Lúc đó tớ nghĩ mua game gốc lại hay hơn , tầm 1-2 năm mới hack dc thì giá tầm dưới 200k mua về vừa chơi đĩa gốc vừa sưu tầm

traneupcqk · 21/1/12

[video=youtube;r2AreZcCe2c]http://www.youtube.com/watch?feature=player_embedded&v=r2AreZcCe2c[/video]
có hướng dẫn cài PKG file cho OFW 4.0 này
ở trên ps3-hacks chắc cũng ko phải fake

power8000 · 21/1/12

mình k rành về hack ps3 lắm ,cho hỏi cài file pkg thì làm được gì vậy !

haihieu003 · 21/1/12

power8000 nói: ↑

mình k rành về hack ps3 lắm ,cho hỏi cài file pkg thì làm được gì vậy !
Click to expand...

cài pkg giúp ps3 chạy đc các ứng dụng khác, crack game, hỗ trợ chơi game .......

SienRyu · 21/1/12

oOziczacOo nói: ↑

Đâu phải game nào đỉnh cũng hợp khẩu vị của mình đâu trong khi game mới ra có mấy cái kết kinh khủng kìa >.< !!!
Click to expand...

Đang nói tớ mà!

Mà nói thế thôi chứ mấy thằng game mới như DS, Dirt 3, Batman......cũng đag thèm chảy cả dãi ấy chứ!

Đăng nhập

[Rumors] Sắp có CFW 4.00 chơi game ko cần USB hack, ko đĩa mồi

zZigxZagz Persian Prince Lão Làng GVN

maxxxpham Mr & Ms Pac-Man

babylove243b Dragon Quest

duoq Donkey Kong Lão Làng GVN

princetimmiz Youtube Master Race

minhjirachi Mario & Luigi

taituxdseller Persian Prince

babylove243b Dragon Quest

mami9x Youtube Master Race

aaaaaaaaaaaaaaaa Dragon Quest

haihieu003 Dragon Quest

minhjirachi Mario & Luigi

maxxxpham Mr & Ms Pac-Man

SienRyu One-winged Angel Lão Làng GVN

oOziczacOo Mega Man Lão Làng GVN

taituxdseller Persian Prince

traneupcqk The Warrior of Light

power8000 Donkey Kong

haihieu003 Dragon Quest

SienRyu One-winged Angel Lão Làng GVN

Chia sẻ trang này

Đăng nhập

[Rumors] Sắp có CFW 4.00 chơi game ko cần USB hack, ko đĩa mồi

zZigxZagz Persian Prince Lão Làng GVN

maxxxpham Mr & Ms Pac-Man

babylove243b Dragon Quest

duoq Donkey Kong Lão Làng GVN

princetimmiz Youtube Master Race

minhjirachi Mario & Luigi

taituxdseller Persian Prince

babylove243b Dragon Quest

mami9x Youtube Master Race

aaaaaaaaaaaaaaaa Dragon Quest

haihieu003 Dragon Quest

minhjirachi Mario & Luigi

maxxxpham Mr & Ms Pac-Man

SienRyu One-winged Angel Lão Làng GVN

oOziczacOo Mega Man Lão Làng GVN

taituxdseller Persian Prince

traneupcqk The Warrior of Light

power8000 Donkey Kong

haihieu003 Dragon Quest

SienRyu One-winged Angel Lão Làng GVN

Chia sẻ trang này

Tìm kiếm hữu ích