flukes1: we have full control of lv1 and lv2 from our test application running as a normal pkg under gameos
flukes1: the issue with lv2 pokes causing shutdown was caused by some protection added in 3.55
flukes1: we found it and disabled it
flukes1: i’m not finished
flukes1: this is the bit you won’t like: there will be no public release
flukes1: as i said, ill release some info
flukes1: if you want BMs to run on 3.55 you need to compromise lv1 and lv2
flukes1: well I seriously wish I could release all this shit at no personal risk
flukes1: I like you guys but it’s not worth it
flukes1: if they know it was me, they can still say it was me and prove it by looking though my computer etc etc
flukes1: so no, i can’t just release it anonymously
flukes1: tbh though
flukes1: the only difficult part is disabling lv2 memory protection
flukes1: and that information will become public soon
flukes1: i’ll post a video on youtube on sunday when I get home
flukes1: game running from hdd under multiman
flukes1: i’ll do a video, i guess sony can’t kick off about that
< +flukes1> just a heads up: I will shortly be releasing info on how to get complete access to lv1 and lv2 from an application running under gameos
< +jbc> sweet.
< +flukes1> next few days probably, just want to see what happens with the court saga
< @rck`d> flukes1: sploitz?
< +flukes1> no
< @rck`d> patched firmware? :/
< +flukes1> yeah, plus a shitload of userland code
< +flukes1> but the fw patches are tested and stable
< +flukes1> modifying firmware is extremely easy compared to fully working lv1/lv2 peek poke

UPDATE: Our man, flukes1 has popped up again in the IRC just now making some further explanation about his upcoming “unreleased” hack and also the possibility to “decrypt” future firmware updates (3.55+) from Sony to the PS3 console.
< @flukes1> sucks that i can’t do anymore than that
< @flukes1> if my identity wasn’t known, i probably would
< @flukes1> you just have to google my nick to see who I am though, it doesnt take a team of sony rocket scientists
flukes1: i bet they could still screw up though
< @flukes1> hah
That reminds me flukes1, I had a question for ya if you don’t mind. It’s not about release times or anything, but about the hack itself.
< @flukes1> fire away
This method you found for gameos stuff messing with lv2, does that mean apps still have to be signed until an app is loaded to patch up lv2?
< @flukes1> i think running totally unsigned apps requires a lv2 + vsh patch
< @flukes1> technically you can patch stuff into lv2.self without editing lv1 at all
< @flukes1> but we didnt want to do that because of brick risk
< @flukes1> can make them work with a bit of work
< @flukes1> we dont really care now though, stuff can be signed
< @flukes1> s3ph: yes
< @flukes1> any patch done on the flash is highly risky
< @flukes1> as you know we bricked 3 ps3s just patching in peek/poke to lv2
we can sign now but what is sony adds more keys ?
arcadekid: then we get the new keys via the metldr key i believe
< @flukes1> most people don’t understand what the metldr keys mean
< @flukes1> it means that any future firmware from sony can *theoretically* be decrypted
< @flukes1> we will not be able to sign stuff for future firmware versions
Clearly with 3.60 Sony will disable tha actual signing keys..
< @flukes1> it will be possible to create a modified version of a future firmware update, everything re-signed with the old keys
flukes1: how long you been coding? what language did you pick up first?
< @flukes1> noxil: since I was 11, PHP
check your paypal acc flukes if you see someone donated you 1$ your in trouble
< @flukes1> someone did