The above video goes away if you are a member and logged in, so log in now!
Why does the firmware have to be patched if we have signing keys.
Why does the firmware have to be patched if we have signing keys. –
Maybe I misunderstood fail0verlows demo but if we have the keys to sign everything then are they only patching the firmware so it will work with USB drives?
Why do we need to mess with the firmware at all if we can sign things just like sony does, meaning they would work on OFW?
If it's just for the syscalls for backup managers I understand..if it's for something more I do not.
fail over flow is onl trying to impliment linux
if you dont wanna play backups you dont need to install any cfw
you can just install signed homebrew, thats all
Mostly to implement the syscalls that we have on our jailbroken consoles.
I mean u have a point, but rly cfw jst for homebrew is somethng cool u could show off to ur friends lol
Ok finally, that totally makes sense. Thanks for the answers. It's what I thought but I hadn't seen a single person ask that question.
Originally Posted by mrelectro713
Right but if the homebrew is signed correctly, you shouldn't need the jailbreak or a CFW unless it's just to enable syscalls for backup loading or if it is needed to load the homebrew from a USB stick.
Originally Posted by neimato1
Well, but we can't do npdrm, which is why you need geo's CFW to install the homebrew.
Originally Posted by JTMON
Once it's installed, you ought to be able to go back to 3.55 OFW and all your homebrew will probably still work (once you install it on Geo's modified).
Well Geo has the decryption info for that and stated he's not going to release it so while we can't NOW, some dev should be able to get to that yes?
Originally Posted by Wutangrza
The entire thing is one big mess atm, I would stick to 3.41 till the keys finally get leaked.
I'd like to know why syscalls can't be enabled within a signed homebrew app instead of messing around with firmware?
to do that they would have to find a hole in lv2, i guess they are not willing to do that so they are hardcoding the patched directly to lv2 for whatever reason.
Originally Posted by dem0n
it would be a better solution to have a sprx load at boot that exploits lv2 on-the-fly instead of hardcoding it like they are now. but flukes1 is the only one really looking into it and thats the route he is going so its really the only way it will be done i suppose.