 |
Thanks for that guys.Originally Posted by sk group
People should have realised that he hadn't even received his dev board yet lol...
xorloser forum should now be listed as UNRELIABLE site due to how easy it is to hijack a name (its easy, just type in a name and post!)
Well, he stated the following as a solution from here onward: http://xorloser.com/?p=297&cpage=17#comment-2329
That said, let's keep this thread on topic and await news after the real graf_chokolo gets his development board.xorloser says: due to the ridiculous number of worthless posts, i have decided to moderate all posts for a while.
i will only be allowing only useful posts, that is posts that give actual information or ask actual meaningful questions. all other posts will go into the trash.
i will not allow any posts asking about when keys or other crap will be released. i will also not allow any “good work guys” style posts, not because i dont think the work is good, but merely because i dont want this comments section filling up with more uneeded posts that make it hard for ppl to find real info between.
since i will have to confirm every post, it may take a unmber of hours even for worthwhile posts to appear. this is because i have many other things better to do than to moderate posts 24/7. when i get time i will see about going back thru the existing posts and removing all the crap posts just leaving the useful ones. but this may or may not happen as my time is limited as it is. (if i had more time i would do useful things like more actual posts on this blog)
I remember the same thing happened with Geohot's blog, at one point it was completly unreadable and unreliable.
Makes you wonder if it are kids or sony employees.
A forum is always better then a blog, its much harder to steal someone's name their (unless you have hacked there password) there's always 50/50 percent chance on a blog it is fake, sadly this was one of them
tbh, it was "too good to be true"
We need to reverse engineer E3's Update file and more news: ecliPS3 announced that the downgrade function will work in 2 days on their dev-board and I have been wondering...
A snippet from key.h of psgrade:
const uint8_t jig_key[20] = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
};
Won't it be a great idea to bruteforce it? I mean, its only 20 characters... but trouble is compiling, flashing and trying!!! anyone have any ideas?
Last edited by Luckluka; 12-05-2010 at 01:02 PM Reason: Automerged Doublepost
Well even with a big community like this, if someome made "packets" and everyone let's say tried 30 or 50 (that's a pretty good amount of time), it's still a lot of combinations, sadly.
I don't remember my math studies but its something like 20^19 x number of valid characters (pardon me if that's unexact, I'm just saying there's A LOT of combinations).
Almost correct. Since it's hex, you have the full range of 256 characters and 20 spaces (160 bits), this makes 256^20 = 1461501637330902918203684832716283019655932542976 possibilities.
Good luck with that
Even assuming each flash chip could take 10,000,000 writes (not very likely), it'd still take 146150163733090291820368483271628301965594 chips/PS3s to try them all.
The thought has crossed my mind, but we're better off making educated guesses for now. Random shots in the dark might hit the key, but then it's all about luck.
Does anyone know if the key implementation is vulnerable to a timing attack (no, I don't expect any 360 hacks to work so don't even bother unless you actually know)?
