they actually do encrypt the elf data sections on the fself and have fself + decryption support handled in lv2 but part of the routine is decrypted through the dongle, it'd be possible to dump it from ram, but honestly, I don't own a dongle and I am not interested
Decrypting from the ram? 3.73 keys can be caught decrypted from the ram if the boot sequence isn't different from previous firmwares, so sorry, not going to happen anytime soon.
Math is talking about the specific encryption that KADO uses. Which aren't 3.73 keys. So it will be easy for an experienced person to get the required information from ram. It's a piece of cake basically. So still there's absolutely no worries.
As master has said to me before, encryption does not mean keys. So keep that in mind. They are just encrypting the elf data sections. Not "signing it" with 3.73 keys.(or else they wouldn't be able to use them without 3.73 keys. Which they don't have. They completely went around that by using the DEV PSN fselfs.
Signing does not always equal encryption, like in this case. (err reverse that. encryption does not always equal signing with keys.)
Anyways I need a nap. I'm knackered. Catch you all later. Anyone needs to ask me something, shoot me a PM.
http://deviant-generation.com/ - my site. Contact me, Korn, and gDrive. I'm the most active but they do come over to speak to me. Likewise it's always a place to send them a message when you need to. Plus you can meet my graphics team!
The Following 2 Users Say Thank You to xPreatorianx For This Useful Post:
So there's masterdisc encryption + additional dongle decryption routines involved. It means no way to get these eboots working without reversing dongle itself.
It may be easier to get 3.6+ keys instead.