[18:37:41] <@neimod> where is the logo file located usually?
[18:37:52] <@neimod> of a 3ds app
[18:37:57] <@neimod> exefs? romfs?
[18:39:04] <@neimod> hmm exefs
[18:39:09] <@neimod> interesting
[18:39:35] <Brian1117> do you need a homebrew channel logo? ;)
[18:39:49] <@neimod> things have started to become very interesting
[18:40:41] <@neimod> not quite raw, and yet still decrypted
[18:42:20] <@neimod> interesting times ahead indeed :)
[18:43:04] <Brian1117> someone start making a homebrew channel logo, neimod is going to need it
[18:43:26] <@neimod> oh
[18:43:35] <@neimod> i don't think homebrew on 3ds is going to be possible at all
[18:43:46] <Brian1117> :o
[18:43:50] <Brian1117> elaborate
[18:43:58] <@neimod> and i'm 99.9% certain when i say that
[18:44:33] <@neimod> atleast, not with a pure software solution
[18:44:54] <Brian1117> well thats interesting
[18:45:12] <@neimod> i've said it before
[18:45:16] <Brian1117> id ask why but i wouldnt understand any of it
[18:45:50] <@neimod> one of the problems is that you can't execute new code from an exploit (even if there was one to begin with)
[18:47:08] <@neimod> the only thing your exploit could do, is jump to existing code, and somehow that should unlock homebrew?
[18:47:41] <@neimod> there is no facility to load new code into the system without finding *another* exploit to break free from the kernel (OS)
[18:47:56] <@neimod> all the while doing that, from already existing code (because you can't add new code in yet)
[18:48:36] <@neimod> only the code pages are marked as execute and read-only, the rest of memory canot execute program code
[18:48:54] <@neimod> *only the code pages are marked as execute and read-only can execute program code, the rest of memory canot execute program code
[18:49:13] <@neimod> so
[18:50:02] <@neimod> finding a solution to these constraints is very difficult, if not impossible
[18:50:23] <Treeki> so.. when's the 3DS jailbreak coming? tomorrow, right? :p
[18:51:35] <@neimod> with hardware solutions, you can loosen these constraints a bit, making exploitation more practical
[18:56:30] <@neimod> a tiny ram interposer for example, would do the trick
[18:56:44] <@neimod> but that's something not everybody can do at their home
[18:57:22] <@neimod> not to mention the signal integrity when running at full clockspeed
[18:57:43] <@neimod> (even though, it could dynamically be lowered for when it's time to patch memory)