Hacking 3DS Firmware has been decrypted

  • Thread starter Thread starter OscarRamos
  • Start date Start date
  • Views Views 192,888
  • Replies Replies 440
  • Likes Likes 6
Status
Not open for further replies.
40 minutes ago, the github was updated yet again with whatever this means: "refactored key related code. added support for fixed system key"

I apologize for posting this, I'm sorry if I'm going wildly off topic or flooding this thread. I'll stop, I just figured it is worth pointing out the momentum. Report this post for deletion.

https://github.com/3dshax/ctr

wtf is all this? https://github.com/3...b8975edbe007e0c

Does he have the common key or is that just a space to add it once he has found it?

It doesn't seem likely, from my experience as a programmer it's just some error check.

EDIT: There was already a function called " setting_is_common_key_valid() " before, he just renamed it for " settings_get_common_key() " nothing to get alarmed about

Actully do you know if he actully changed its function, cause then it might be somthing. Where does "settings_get_common_key()" point to?

It points to here, the settings.c file:

https://github.com/3...tool/settings.c

unsigned char* settings_get_common_key(settings* usersettings)
{
if (usersettings && usersettings->keys.commonkey.valid)
return usersettings->keys.commonkey.data;
else
return 0;
}

It's a simple true or false function that returns a pointer to an unsigned char
 
40 minutes ago, the github was updated yet again with whatever this means: "refactored key related code. added support for fixed system key"

I apologize for posting this, I'm sorry if I'm going wildly off topic or flooding this thread. I'll stop, I just figured it is worth pointing out the momentum. Report this post for deletion.

https://github.com/3dshax/ctr

wtf is all this? https://github.com/3...b8975edbe007e0c

Does he have the common key or is that just a space to add it once he has found it?

It doesn't seem likely, from my experience as a programmer it's just some error check.

EDIT: There was already a function called " setting_is_common_key_valid() " before, he just renamed it for " settings_get_common_key() " nothing to get alarmed about

Actully do you know if he actully changed its function, cause then it might be somthing. Where does "settings_get_common_key()" point to?

It points to here, the settings.c file:

https://github.com/3...tool/settings.c

unsigned char* settings_get_common_key(settings* usersettings)
{
if (usersettings && usersettings->keys.commonkey.valid)
return usersettings->keys.commonkey.data;
else
return 0;
}

It's a simple true or false function that returns a unsigned char
Ah alright, thank you. Seems to just be a simple name change....
 
I'd give my right nut (and left) for a 3DS hack! I'm so sick of the bullshit region lock Nintendo threw at us. That's something I give Sony credit for. They know how to do shit.
 
  • Like
Reactions: 1 person
Ah alright, thank you. Seems to just be a simple name change....

I only program in Java, not C++, so I'm not sure of all that's going on there, but it looks like most of the code in that change added a check to see if the NCCH (the container for 3DS files) is encrypted or not or if a key that is supply is valid. There doesn't appear to be any sort of code in there for finding a key, only checking if one is valid, but I may be wrong.
 
Ah alright, thank you. Seems to just be a simple name change....

I only program in Java, not C++, so I'm not sure of all that's going on there, but it looks like most of the code in that change added a check to see if the NCCH (the container for 3DS files) is encrypted or not or if a key that is supply is valid. There doesn't appear to be any sort of code in there for finding a key, only checking if one is valid, but I may be wrong.
I agree (I know only java as well lol, but even then prob alot less then you)
 
Ah alright, thank you. Seems to just be a simple name change....

I only program in Java, not C++, so I'm not sure of all that's going on there, but it looks like most of the code in that change added a check to see if the NCCH (the container for 3DS files) is encrypted or not or if a key that is supply is valid. There doesn't appear to be any sort of code in there for finding a key, only checking if one is valid, but I may be wrong.
I agree (I know only java as well lol, but even then prob alot less then you)
I guess it should be pointed out though that if he did decrypt the system key, it's not going to be posted in his git repo.
 
  • Like
Reactions: 1 person
Ah alright, thank you. Seems to just be a simple name change....

I only program in Java, not C++, so I'm not sure of all that's going on there, but it looks like most of the code in that change added a check to see if the NCCH (the container for 3DS files) is encrypted or not or if a key that is supply is valid. There doesn't appear to be any sort of code in there for finding a key, only checking if one is valid, but I may be wrong.
I agree (I know only java as well lol, but even then prob alot less then you)
I guess it should be pointed out though that if he did decrypt the system key, it's not going to be posted in his git repo.
True and I suppose if he decrypted the firmware, the key could have been right there in plain text right >.>; (doubtful).
 
the possibility exists that some team develop some exploit
already working in some exploit?
No one outside of neimod and maybe a few others knows what's going on, so who knows. Probably not though since no one knows if encryption's been broken....
the possibility exists that some team develop some exploit
 
the possibility exists that some team develop some exploit
already working in some exploit?
No one outside of neimod and maybe a few others knows what's going on, so who knows. Probably not though since no one knows if encryption's been broken....
the possibility exists that some team develop some exploit

True but unless they find a way to repack and install the firmware, we are pretty much in the same spot since we still cant sign anything.... (unless of course the common key is just there in the files that were unencrypted..... If thats even happened lol)
 
the possibility exists that some team develop some exploit
already working in some exploit?
No one outside of neimod and maybe a few others knows what's going on, so who knows. Probably not though since no one knows if encryption's been broken....
the possibility exists that some team develop some exploit

we still cant sign anything...(unless of course the common key is just there in the files that were unencrypted..... If thats even happened lol)

No, the common key CANNOT sign anything.
Regardless Nintendo wouldn't leave it so carelessly. Leaving it plaintext in the firmware would be like leaving your house key under the mat.
 
  • Like
Reactions: 5 people
but with a common key you can decrypt cant you? is that not the more important part of the equation ? with p3 there was only decrypt with common key and some fake sign tool right?
 
but with a common key you can decrypt cant you? is that not the more important part of the equation ? with p3 there was only decrypt with common key and some fake sign tool right?
The only real way to run unsigned code is with an exploit of some kind (buffer overflow is usually the most common). Decrypting the code is a good step to finding vulnerabilities that can lead to an exploit, but it's not guaranteed. AFAIK, the latest PS3 firmwares have been decrypted for a while but there has yet to be a CFW released for anything past 3.55 (4.10 is the latest?), but I may be wrong about that.
 
4.21 is latest i think no cfw beyond 3.55 except i think dh 3.56 but yeah ,new 3.60+ keys have been released and now tb dongle drm has been cracked too
 
The common key isn't in the firmware, its somewhere in the hardware. like the wii key where in broadway.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum