https://github.com/Reisyukaku/ReiNX?files=1No it is not! It is only naehrwert's hwinit code. The rest of this CFW are only binary blobs.
?
https://github.com/Reisyukaku/ReiNX?files=1No it is not! It is only naehrwert's hwinit code. The rest of this CFW are only binary blobs.
I'm curious if it really ever become open source.It's open-source. The only thing that's closed-source (for now) is the signature patches, and I think that's because Reisyukaku doesn't want someone forking them into a renamed CFW that overshadows ReiNX before they're done.
Well, then explain this to me you smartass:Wow lol
https://github.com/Reisyukaku/ReiNX/tree/master/data
you are the best part of our voice chat right now, keep goingI'm curious if it really ever become open source.
making it work at all is the real issue. we've been trying it on everyone's switch, and it's just not playing nice right now.I would compile it with sig check patches baked in, but not release it.... Not at all hard to do, but of course,someone would fudge it all.
Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.The unpack apparently fixed that, it just turns out and idiot with pirated IDA Pro still has no idea what they're doing.
Those that do (Rei) managed to see everything just fine.
Once everything is working properly and ReiNX is officially released (and not a work-in-progress), I don't see why it wouldn't be truly open-source.I'm curious if it really ever become open source.
Mm, I guess that makes sense. The actual firmware code is very much visible, thoughhttps://github.com/Reisyukaku/ReiNX/tree/master/data
I believe it's about the `.kip` files, which just sit there and get copied.
Not necessarily, PS3 CFWs and backup loaders had support for split files on fat32 external drives.If this is the case Rei will have to fix this because we will need exfat once .xci and .nsps are working. Please correct me if im wrong!
I'm curious if it really ever become open source.
--------------------- MERGED ---------------------------
Well, then explain this to me you smartass:
https://github.com/Reisyukaku/ReiNX/tree/master/data
You're mostly correct. The easier thing to do is to take the few features that make SX OS worth anything and implement them in an open-source CFW.Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.
Now unless I'm wrong and one of them have said that they see how the patching works, and either won't or can't implement it for some reason or another, it's still obviously not as simple as a copy+paste operation.
Rei definitely managed to get a looksee around and see what makes SX tick: https://twitter.com/Reisyukaku/status/1016804828901756929Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.
Now unless I'm wrong and one of them have said that they see how the patching works, and either won't or can't implement it for some reason or another, it's still obviously not as simple as a copy+paste operation.
First, I agree with nearly everything you said, so don't get me wrong.Are these guys for real.... Come on guys, compile the cfw, build a bin for yourself and try it out. Its our very first CFW ^^ Happy days allright! Anyways, Rei allready stated a million times before, like so many others the cfw is a WIP, this means Work In Progress... (S)he is not done, he hasnt closed the software or anything (open source ftw) and sig patches are coming asap. Give it some time and i think we all will be running reinx in one way or another in about 2 months.
Again, great job on publising the code rei, we love it And dont bother about the flamers, a guy has to complain after all things said and done apparently
First, I agree with nearly everything you said, so don't get me wrong.
That being said, the signature patches are technically closed-source right now. You can read my earlier post on why I find that mildly disconcerting.
For now, nothing. It opens the door to a functionally modular CFW, but modules don't exist yet. More importantly, signature patches will be implemented in the near-ish future.What can you do with this CFW that you can't do with Hekate?
All of the work being done on signature patches is figuratively being done behind closed doors. While that's Reisyukaku's prerogative to do it like that, it makes the work on signature patches technically closed source for the time being.Ive read ur post and im not saying we dont 'have sig patches', we dont have them because there not in the main repo and closed source. Im not saying u cant do it, its just a bit of a sidetracking to get them to work. That said, its modulair, u can add almost anything i guess
Your switch doesn't have the exfat Update then. Maybe that's the error, after booting.
Try formatting it to fat32
ask a question about the work and it will be answeredAll of the work being done on signature patches is figuratively being done behind closed doors. While that's Reisyukaku's prerogative to do it like that, it makes the work on signature patches technically closed source for the time being.