Hacking 3DS update process analyzed

[machomuu]

You just keep up what you are doing RoyalCardMan. These forums are full of Nay sayers on every thing. At least you are trying to figure it out. Those who bash, most likely have little or no idea on where to start. They just sit and wait for some one else to do the work.

That can be said about the entire world. I may be a neutral party, but I will I this, I will move to the nay saying side if I see more of this slandering of the Temp or any whining on Royal's part. While he hasn't whined yet, which is good, it pisses me off to see people like the aforementioned who do as ferret did. The worlds greatest inventors and researchers took the abuse and didn't complain. They didn't insult anyone, they didn't just "stop", they didn't just go away crying, and that's definitely not what I what I want to see here. I only want to see you "stopping" if you hit a brick wall or or just feel like stopping. Also, Nathan is doing a good thing, he's trying to prove that you can't do it, which is important when doing something like this as it helps you notice the flaws in your research and prove and adjust them accordingly.

 

[Arisotura]

So, I will continue trying to hack the Nintendo 3DS, and no one is going to stop me.

Beware, Nintendo!

Also, friendly tip, RoyalCardMan: try reverse-engineering /dev/rand instead of Nintendo's files, you may obtain better results.


(there was going to be a serious post here, but it'd mostly be repeating what others said: trying to reverse-engineer encrypted crap is a waste of time)

 

[Nujui]

Actually, to quote a quote made from a quote...

Spoiler

QUOTE(ChrisRX @ Jul 26 2011, 06:49 AM)
I've said it many times before but I guess it's still relevant. The people who are actually smart enough to break software and hardware security are not the sort of people who frequent this forum. They have much more knowledge than most (if not all) of us and everything that gets suggested I'm sure they have already thought of.

In reality it's going to be nowhere near as simple as your suggestion and there would be months if not years of additional work. As I'm sure you know you can't just find a key and then poof, homebrew. There would be all sorts of encryption algorithms to crack on the software side and even more to investigate on the hardware side.

I do commend you for actually sounding more intelligent than most people who make suggestions but in short, if we think of anything that may help towards the hacking efforts, chances are the experts have already tried it.

He said it best.

 

[RoyalCardMan]

Since I might as well do something else since people won't accept my intellegents.
I am just going to start from the very beginning(Where I started 10 years ago) and learn Python again.

 

[Arisotura]

Your intellegents should know that trying to reverse-engineer encrypted code is a waste of time (has been said in this thread for the 53th time or so). You'd be better off hacking your toilet or something...

 

[raulpica]

This thread isn't going anywhere. It'll just became a bashing-fest, eventually (like it wasn't one already).

@RCM
Feel free to open another thread, but I'm sure that if you won't change your hacking methods, it'll end up like this one.

And with this, I'm closing this.

try reverse-engineering /dev/rand instead of Nintendo's files, you may obtain better results.

Good one.