So in that case, it's not a bootrom exploit itself. Good god.THAT RSA CODE IS IN THE PROTECTED BOOTROM
Good. God.
So in that case, it's not a bootrom exploit itself. Good god.THAT RSA CODE IS IN THE PROTECTED BOOTROM
Good. God.
cmon I´m feeling like the water type z-move was used on meSo in that case, it's not a bootrom exploit itself. Good god.
I can't believe I'm reading thisSo in that case, it's not a bootrom exploit itself. Good god.
I just posted that and you said I was rude.updated the op and thanks
Just ignore the people who don't realise exploiting a bug in the bootrom is a bootrom exploitcmon I´m feeling like the water type z-move was used on me
totally confused with everything now, half the users here say my op is correct he other ones say I completely messed it upI just posted that and you said I was rude.
k thanksJust ignore the people who don't release exploiting a bug in the bootrom is a bootrom exploit
We aren't touching the bootrom, it's readonly anway, all we are doing is exploiting the fact it only requires half assed signatures to load the firmware which can be brute forced since its only a couple bytes that are requiredlmao I'm done.
The sigpatch doesn't exploit the bootrom itself, the actual bootrom exploit exploits it, lmao.
All the sigpatch does is use the exploited bootrom to it's advantage, to enable FW signing.
Have a nice day!
I think the misunderstanding here is the fact that an exploit, in your definition, can only mean taking over control of the code. That is not the case, defeating the bootrom's ability to verify firmware code as correctly signed is definitely exploiting a flaw in the bootrom itself.lmao I'm done.
The sigpatch doesn't exploit the bootrom itself, the actual bootrom exploit exploits it, lmao.
All the sigpatch does is use the exploited bootrom to it's advantage, to enable FW signing.
Have a nice day!
I think the misunderstanding here is the fact that an exploit, in your definition, can only mean taking over control of the code. That is not the case, defeating the bootrom's ability to verify firmware code as correctly signed is definitely exploit a flaw in the bootrom itself.
We aren't touching the bootrom, it's readonly anway, all we are doing is exploiting the fact it only requires half assed signatures to load the firmware which can be brute forced since its only a couple bytes that are required
XD You might wanna edit it thought lol it should be "realise" not "release" oops lolFine btw @KevinX8 added your post to my signature actually that was really funny
pretty muchit basically turns this
into this
gonna do xDXD You might wanna edit it thought lol it should be "realise" not "release" oops lol
" relealise" Achievment unlocked! Invented a new word when fixing an errorgonna do xD
damn that literally killed me, I´m dumb" relealise" Achievment unlocked! Invented a new word when fixing an error
What's up with the scene lately? Everyone has become such naysayers. Like this is cool stuff! Another means of booting into CFW? And even faster than A9LH! That's cool as hell!
I don't remember this much pissing and moaning when A9LH was revealed.
Or we could just be happy that we are getting somewhere. This is actually big stuff! We will have even more control over the system than ever before!Some have been spoilt for choice with CFW and means of putting it on their 3DS'.
They'd no doubt be a little more humble if things like this were held back until it's needed instead of just throwing it into the basket of current CFW installation methods etc.
This is quite possibly the dumbest thing I've read all day.lmao I'm done.
The sigpatch doesn't exploit the bootrom itself, the actual bootrom exploit exploits it, lmao.
All the sigpatch does is use the exploited bootrom to it's advantage, to enable FW signing.
Have a nice day!