Hacking [WIP] open source Kernel access on 3DS

  • Thread starter Thread starter aliak11
  • Start date Start date
  • Views Views 232,744
  • Replies Replies 1,003
  • Likes Likes 42
Status
Not open for further replies.
I know but the fact that it is open source will alow others devlopers to do it so...

Exactly, I'll just give you a protip: Don't announce features that haven't been implemented into something. The 3DS scene is (sadly) mostly based on people with moral standing against P-word and also, I don't believe anyone would like to get jumped the same way DarkAlex and such did when they made such things possible on other platforms. As much as I'd like it to have my game backups playable, I'm not holding my breath for it.

EDIT: Ninja'd (kind of) XD
 
Advantages to closed source? No one can improve upon the software outside of whoever has access to it...meaning it's certainly possible for bugs to sit out there and never be fixed until if/when one of the developers becomes aware of it. Not quite as much of an issue with open source. Enough said. And yes, in my eyes, and probably others here, it is that black and white (mind you, I'm a software developer myself, just not so much in the ASM/C world).
 
It is never that black and white. There are advantages and disadvantages to both.


What+happens+in+the+brain+when+you+die+like+is+_1713d09caced081e1c01be9b503d7ac5.jpg
 
<sniperoni>


In general, open source is better, and security through obscurity almost never works. However, some things may contain sensitive code/other stuff which really shouldn't be included in source files publicly (ie snippets from FIRM and whatnot). Not to mention that there really isn't any outside gain to creating a full on open source warez-capable loader. It's not like I can put on my resume or something that I made a particular CFW which eventually was turned into a tool for piracy, that would reflect negatively on myself because I didn't take the proper precautions before doing the project to maintain proper ethics within another person's ecosystem which I'm hacking into.

Now that's not to say that closed source is always the best, some things like homebrew and games I'd say go 100% full open source, because those can improve greatly with community support. If you look on my Github you'll find plenty of research and utilities which I keep the source open for, and with good reason. So in reality both have their ups and downs. Everything has a proper tool for the job; you can't screw a screw with a hammer, it just doesn't work.
 
In general, open source is better, and security through obscurity almost never works. However, some things may contain sensitive code/other stuff which really shouldn't be included in source files publicly (ie snippets from FIRM and whatnot). Not to mention that there really isn't any outside gain to creating a full on open source warez-capable loader. It's not like I can put on my resume or something that I made a particular CFW which eventually was turned into a tool for piracy, that would reflect negatively on myself because I didn't take the proper precautions before doing the project to maintain proper ethics within another person's ecosystem which I'm hacking into.

Now that's not to say that closed source is always the best, some things like homebrew and games I'd say go 100% full open source, because those can improve greatly with community support. If you look on my Github you'll find plenty of research and utilities which I keep the source open for, and with good reason. So in reality both have their ups and downs. Everything has a proper tool for the job; you can't screw a screw with a hammer, it just doesn't work.

Fair enough though I still disagree slightly about the screw analogy, also sniperoni made me hungry :/
 
  • Like
Reactions: lPolarisl
Don't worry. Many developers don't understand C and ARM assembly. There are so many dirty codes :P
(Of course, there are developers who writes nice code. Some developers who can't write good code may be good for reverse-engineering.)

I hate to bring this thread back OT, but.....

The GIT shows nothing has changed in three days, any chance of working on this again soon?
It gets a little boring reading the same debates over-and-over while we wait to play with new Alpha's.

Did you get your hands on a Cubic Ninja for your N3DSXL yet?

Just ask'n...
 
-SNIP- It's not like I can put on my resume or something that I made a particular CFW which eventually was turned into a tool for piracy -SNIP-

Hate to have to call you out on this, but your argument against enabling piracy doesn't hold weight when you're making source contributions to a GBA emulator....next to no one uses emulators legitimately. Probably fewer people than what would use a 3ds rom loader legitimately. I suppose that's neither here nor there, though.
 
  • Like
Reactions: Margen67
Hate to have to call you out on this, but your argument against enabling piracy doesn't hold weight when you're making source contributions to a GBA emulator....next to no one uses emulators legitimately. Probably fewer people than what would use a 3ds rom loader legitimately. I suppose that's neither here nor there, though.


Come the fuck on. The GBA is a dead platform. You can't give Nintendo money in anyway by purchasing a GBA or GBA games in 2015.
 
  • Like
Reactions: Zidapi
Although personally, I'd agree. The way the laws are written though, piracy is piracy. Doesn't make much difference if a game was released 5 minutes ago, or 20 years ago. Also VC is a thing.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum