UPDATE: Regarding the recent 3DS banwave

fb-3ds-400x400.jpg

It appears that users are being banned from 3DS online services, en masse. There's no direct cause right now, and seemingly no linking factor. This post is meant as an announcement for users, to be wary, and that GBAtemp will keep you updated as soon as more info rolls in. If you have been banned, please post in the thread below, and we will try to keep tabs on the situation. To be extra sure, it can't hurt to turn off your 3DS's wireless capabilities, so you might as well do that for now.

Edit 1: it appears that e-Shop access isn't restricted if you are banned.

Edit 2: A caller to Nintendo reported that the company said this ban is due to "unauthorized software usage".

Edit 3: @LinkSoraZelda is collecting info. Contact him if you are banned.

Edit 4: Click and fill this out if you were BANNED.

Edit 5:
[11:28:19 PM] Clector: Curiously the page of that error in Nintendo Support website used to have this:Error Code: 002-0102 Situation: You receive the error code 002-0102 when attempting to connect online. What to Do: If you continue to experience this issue, please contact Nintendo by calling 1-800-255-3700. Representatives are available from 6 a.m. to 7 p.m., Pacific Time, 7 days a week.
[11:28:44 PM] Clector: Now it says this: What to Do: If you are experiencing this error code, your Nintendo 3DS family system has been banned due to unauthorized system modifications, play of unauthorized versions of one or more games, and/or connecting to the official game servers in violation of our terms of service. This ban is effective immediately and requests to remove the ban will not be processed.
Thanks to @Joom

Edit 6: Aurora Wright is taking another poll here

Edit 7: Not a lot is known but

There are bans happening, they are happening in all regions.
All models in the 3ds family seem to be candidates for banning.
There is no indication they will be anything other than permanent.
A game or DLC may end up being a cause but there is no one game or DLC that ties banned users together.
The cause or causes are as yet unknown, though it does seem to be related to modifications. Reports of unmodified consoles being banned are as yet unproven.
The banning is tied to something you can modify, thus you can unban. Doing it while the causes are unknown is likely only going to burn a working token though.
There are semi public tokens out there, Nintendo knows how to browse a forum as well as you so don't be surprised if they also get banned.
It does not seem to be limited to a given base firmware version, it does not seem to be limited to any one custom firmware type. There is some speculation that older hacking methods are not being hit as hard but nothing to confirm this yet.
The data collection could have happened this morning, or it could have been months in the making.
A simple check to see is checking your friends list, by itself it will not ban you.
Some are turning their wifi off. It is doubtful this will be of much use and being banned does not seem to come with any downsides that wifi being off will not also mimic.
You may have escaped a ban thus far but it could happen at any point. It could be that they stop in the future, it has happened on other consoles, but you would be living in hope rather than any particularly well founded logic.
The bans are done on the side of Nintendo's servers rather than your 3ds so there is also that.

If you hack your devices/games then their online functionality may be troubled. This has been known for decades, Nintendo seems to have finally caught up with that.

Please continue to share information with the thread or the links in previous edits.

Update 5/30

HOW TO HELP AVOID BANS (we think)​

If I was to guess from the information we have gathered since the ban wave, it seems likely that they are looking for TitleIDs that don't exist. Homebrew shows up in the activity log as the Download Play app, and fake CIA's show up as just ??????. That last one is what I'm guessing they are looking for.

If you are not banned yet or before you unban yourself, go into your friends list, choose settings, and turn off the option to "show friends what game you are playing." This will prevent you from playing games online with friends, so turn it back on when you wanna game with someone, but ALWAYS keep it off when running custom CIAs. Next, go into system settings -> internet settings -> spotpass, and turn off BOTH options. One is auto download software, the other sends system information to Nintendo. Also, make sure you don't have your favorite title set to something stupid like FBI or any other non-Nintendo CIA.

Its VERY likely that these options are what tipped off Nintendo, but we aren't 100% certain yet. The amount of banned people that had one of these options turned on was over 80% for each. If I was to assume that some of those people overlap, its very possible (but not confirmed) that 100% of banned people in the survey had at least one of those options turned on. I personally had all of them off and I have TONS of reasons for Nintendo to ban me.... yet I am not banned (yet).

Another bit of advice: Only run custom CIAs when offline, and after you close them, run a "legit" game like Smash Bros. or something before shutting down or going back online. This way your most recent title won't show up as a fake CIA

Current Theories as to what causes a ban
* SpotPass Settings: 8 users out of 46 users that were banned have SpotPass completely shut off, or SpotPass only (no friends list visibility)
* Firmware Version (Luma, Nintendo): Literally all reports ranged from 10.2+, I can get exact numbers for this if you'd like, but all firmwares were affected.
* Firmware Type (A9LH, B9S): 44 of the 126 B9S users that answered were banned, pattern was mirrored for A9LH users as well.
* Homebrew Titles such as FBI, HBL, Luma Updater, Themely, and freeShop: Literally about 98% of users both banned and unbanned had some combination of these applications installed. However the common ones were: FBI, HBL, LumaUpdater and NTR.
* Save Modification: Equal amounts of users on both sides have reported save modification in some form, either with PKSM or another save editor
* System Transfers: 188 users said that they had not previously system transfered, 61 of those users were banned; 16 users said they transferred from a hacked console, only three of them received a ban; 13 said they transferred from a stock system and likewise were banned. The rest of our sample did not answer this question.
* Activity Log Information: A majority of those who have not been banned have said they had NOT cleaned their activity logs. I can get exact numbers for this too on request.

This information is just what I've found. Like I said, there could be variables or things we haven't even checked for yet. But these are things that I feel should be disproven, at least with the current dataset we have.

  • From the information that we've gathered from some people that have used a packet sniffer such as WireShark, the following data is sent to Nintendo's online gaming servers as soon as the 3DS connects to the internet:
    • Amount of time spent online (timer stops when either the system is disconnected from the internet, or connection drops out, then starts the timer again in a new session when it reconnects to the internet).
    • The game being played and amount of time spent on it during that session.
    • The console's unique hexadecimal ID used in the LocalFriendCodeSeedB, along with it's RSA-signed signature.
    • The console's serial number in which is broadcasted from the SoC and is hard coded in the SoC.
    • Friend Code generated on the Nintendo 3DS system, if one has been generated.
    • Internet connection status (either online or offline).
    • The Nintendo Network ID, if there is one linked to it.
    • Even if the sending of SpotPass Information is switched off, or even hiding your currently playing games. It does not prevent the system from sending currently playing information to Nintendo's online gaming servers, it only hides it from your friends in your friend list (like being invisible on the forum, while mods and admins can still see you). Why? Because even people without a Friend Code on their system have been getting banned too!

  • The following data is NOT sent to Nintendo's online gaming servers:
    • The data from the Nintendo 3DS's Activity Log. Oddly enough, while Nintendo does explicitly state that they collect Activity Log data, they're actually referring to their own server's Activity Log, which always tracks every console's online activity, and keeps a record of them that is stored forever. And is only collected in increments of data through a timer and a currently playing list.
    • Games or apps that have not been played, regardless if they're legitimate or not. You only get tracked when you're online and using that game or app.
    • Using games or apps while offline. Even though it is stored on the 3DS console's Activity Log, that data is NOT sent to Nintendo's online gaming servers.
    • Custom Firmware. Though we can't rule out the possibility of them releasing a 3DS update in the future that adds such function to collect MD5 hashes of files and FIRM data and send them to Nintendo online gaming servers (which would also be updated in a maintenance).

  • Things that people think what happens with consoles, but really doesn't:
    • "LocalFriendCodeSeedB is transferred to the system upon doing a system transfer". This is false, the LocalFriendCodeSeedB remains on the system and does not move to another system.
    • "The console generates a LocalFriendCodeSeedB upon first startup". Again, this is false, the LocalFriendCodeSeedB is made during the manufacturing process at Foxconn. It is generated at the factory, flashed to the NAND flash memory storage, then created as an account on Nintendo's online gaming server and Nintendo eShop server immediately when being manufactured. It is absolutely impossible to generate a LocalFriendCodeSeedB and be able to connect to Nintendo's online gaming server and/or Nintendo eShop server, even if you knew the RSA generation key for it. You'd end up with Error Code 002-0102 "This console's online services have been restricted by Nintendo" if you even tried (the error can either mean two things: The hexadecimal ID doesn't exist on the server, or the request to access the hexadecimal ID has been denied which in other words... banned). So a LocalFriendCodeSeedB generator will NEVER happen! Because it's not worth doing, if it can't connect.
    • Switching off "Currently Playing" information. Once again, this does not hide your online activity from Nintendo's online gaming server, it only hides it from your friends.
    • Switching off SpotPass. Nope, this too doesn't hide your online activity from Nintendo's online gaming server, it only opts-out of receiving SpotPass data, sorry.

So pretty much the bottom line is, if anyone has been using custom apps and/or titles not installed through Nintendo eShop while online in the past, guess what? You're screwed! And it is only a matter of time before your console's unique hexadecimal ID in the LocalFriendCodeSeedB is banned from Nintendo's online gaming server. This will mean, your console can't access the Friend List or play any online functions in games.

If you have been online while using custom apps and/or titles not installed through Nintendo eShop and haven't been banned yet, that's because Nintendo hasn't caught up to you yet. They're still going through each unique hexadecimal ID's Activity Log on their server, and by Activity Log, I mean the Activity Log on their server, not the 3DS console's activity log. And it will be only a matter of time before you're banned too.

Thanks to @Platinum Lucario @MadMageKefka and @ShadowEO !
 

Giodude

GBAtemp's official rock
Member
Joined
May 17, 2015
Messages
5,094
Trophies
1
Age
23
Location
New York
XP
2,761
Country
United States
Has there been any proof that a 3ds that has been banned and unbanned can be banned again. I use fbi, hbl, and around 30 other custom applications, plus the occasional pksm and I'm fine. I was banned during Pokemon moon, but unbanned with another 3ds.
 

Shinusagi

Active Member
Newcomer
Joined
May 25, 2017
Messages
26
Trophies
0
Age
37
XP
75
Country
Argentina
It seems very clear to me with all the evidence gathered thus far.
Which makes me laugh still is the portion of naive guys waiting for Nintendo to come and say specifically why they banned the consoles as if they would do such a thing lol.

Anyway we have no any idea when the next banwave could come, maybe for Christmas or maybe in 2 months... so playing online pirate games is up to each one. I will wait one more week, unban it with a personal LocalSeedB and activate the online only for my legit games.

But I have a problem and BootNTR and InputRedirection won't work since my 3DS doesn't keep connected to my AdHoc unless there is internet shared, it works only few seconds and that's all... anyone can give me a tip on that? Or should I make a new thread about it asking for help? XD
 
D

Deleted User

Guest
Nintendo can see which IP downloads from eShop, that means they can easily guess who downloads legitimately or illegitimately. But meh, it takes too much work so:

My clue is that either Nintendo applied a Software-wide security in their system which will scan stuff like apps, modifications, tweaks and what's currently running in memory or was left in memory [Before you call me out: EasyEAC does that, atleast not everything listed here] (Also, Nintendo doesn't need a system update to apply it. It's done server-side?)
or... You can't hide illegitimate stuff. They might index some stuff, or they will hide it from database from normal users. [Thus why some see "?????"] and then their fun begins.

Fun fact: If you run SysConfigTool on your Wii U, it's visible for others. Even if you see "?????". [Somebody on my friend list ran it and that was weird. It was back in 2014]
 

demounit

Well-Known Member
Member
Joined
Aug 18, 2016
Messages
258
Trophies
0
Age
104
XP
225
Country
wew so much speculation in this thread being treated as fact.

the *only* fact is we have no idea why some people got banned. i'm dipping out of here, see ya next ban wave, bois.
 

MajinCubyan

The Funky Super Saiyan
Member
Joined
Nov 24, 2014
Messages
783
Trophies
2
Age
35
Location
Orre
XP
2,124
Country
United States
I'm not (yet) banned. But my 3ds is a JP n3ds with a US region changed sysnand and the original JP nand on my emunand. Use both fairly regularly, different nnids and friends lists as well. Spotpass turned off on both nands. Generally wifi off unless I'm playing MH.

Hope I don't get banned, but if I do, I wonder if it will affect both or just the one. Only time will tell. If I do, I'll share my experience.
 
  • Like
Reactions: Shinusagi

PedroKeitawa

Well-Known Member
Member
Joined
Aug 15, 2015
Messages
1,042
Trophies
0
Age
34
Website
natsunokaze.altervista.org
XP
1,134
Country
Italy
I was re-reading the varius discussion, especialy the last update, so corret me if im wrong. Nintendo have always have the power to ban user with a mod system, becouse apperently have always see what legit software was running on our system, but only now decide to take action? Somebody in this discussion have borught up the theory about the recent boot9strap, becouse is a mod that give to me (the user) full controll of my sytem, can have couse Nintendo to take action (even if i still hate thet "third party software" that they use since, you know, is a term even use for official game made by other company...so if i play a Capcom o Konami game can i get ban?). So if this his true: Nintendo was ok to use to mod our console before boot9strap come out? Maybe is just a timing coicidence but this was very strange. Again correct me if im wrong on some things.

Also yesterday i decide to unban my self. Just for have some fun with my bf in MHGen at least one last time before the pubblic seed become ban.
But i guess is a good thing that, even after the ban, the console is still usable for the basic stuff.
 
Last edited by PedroKeitawa,

Clydefrosch

Well-Known Member
Member
Joined
Jan 2, 2009
Messages
6,023
Trophies
2
XP
4,621
Country
Germany
so was this place visited by one of nintendos software- and it engeneers or how are we so sure about all the things in the later part of the original post?

irregardless, i suppose we should invest in some kind of money pool to buy a few fresh 3ds' to distribute new friendcodeseeds after every banwave?

assuming theres a wave every month and they dont go and automate the process, we'd be set with a dollar each for the next 12-24 months (old 2ds consoles will only get cheaper too)
 
Last edited by Clydefrosch,

suzsuzuki

Well-Known Member
Member
Joined
Aug 25, 2016
Messages
403
Trophies
0
Age
36
XP
471
Country
Brazil
What I really don't understand is Why Nintendo didn't ban the public seed???

It's public and Nintendo knows about it, it only needs to add on the blacklist! So... what's Nintendo waiting for? Maybe doing a log to ban console IDs and NNIDs? I'm just afraid...
 
  • Like
Reactions: Shinusagi

delete12345

Well-Known Member
Member
Joined
Feb 27, 2010
Messages
695
Trophies
1
Age
32
Location
Taipei, Taiwan
XP
1,276
Country
United States
What I really don't understand is Why Nintendo didn't ban the public seed???

It's public and Nintendo knows about it, it only needs to add on the blacklist! So... what's Nintendo waiting for? Maybe doing a log to ban console IDs and NNIDs? I'm just afraid...
There's a legitimate reason why the public seed is public. I don't know why, but it's named "public" for a reason.
 

MushGuy

Well-Known Member
Member
Joined
Feb 11, 2010
Messages
1,280
Trophies
1
XP
2,584
Country
United States
Feel free to correct me, but I think I might know why some systems were banned and some not: From what I read about SigHax, with it, it is now possible to fakesign FIRMs, and Luma3DS now happens to be one of them, which means that Nintendo can no longer detect if it's signed or not. What does it mean for CFW users? Apparently, the users who were not banned managed to update to SigHax/B9S soon enough before Nintendo was able to detect them, while those who did not update soon enough or did not update at all unfortunately were hit by the banwave. As I said before, feel free to correct me, as I might be missing something in this theory.
 

delete12345

Well-Known Member
Member
Joined
Feb 27, 2010
Messages
695
Trophies
1
Age
32
Location
Taipei, Taiwan
XP
1,276
Country
United States
It's public because someone shared it... just it.
... Which is a legitimate reason.

Because someone "shared it publicly"...

Let's make it known that I'm nitpicking at myself for this.... :wacko:

--------------------- MERGED ---------------------------

Feel free to correct me, but I think I might know why some systems were banned and some not: From what I read about SigHax, with it, it is now possible to fakesign FIRMs, and Luma3DS now happens to be one of them, which means that Nintendo can no longer detect if it's signed or not. What does it mean for CFW users? Apparently, the users who were not banned managed to update to SigHax/B9S soon enough before Nintendo was able to detect them, while those who did not update soon enough or did not update at all unfortunately were hit by the banwave. As I said before, feel free to correct me, as I might be missing something in this theory.

So, you're saying those who had B9S, yet they still are banned afterwards, are banned because Nintendo caught up to them updating to B9S? Doesn't sound right.
 
  • Like
Reactions: suzsuzuki

BARNWEY

Well-Known Member
Member
Joined
Oct 11, 2016
Messages
1,268
Trophies
0
XP
648
Country
United States
I'm considering doing the same, but don't know what does it mean to have (or how to modify it) a modified SecureInfo_A. Could you explain about that stuff? Or link me somewhere to read about it.
At least for now, I've block most of Nintendo's stuff via DNS.
SecureInfo_A contains information about your 3DS; most people edit it to edit the serial code or region. You need a hex editor to edit it, and then go down to the bottom where the serial code is. Leave the first two numbers the same, and edit the rest of your serial code. Save, and inject it...
 

MagicKnight

Active Member
Newcomer
Joined
Sep 21, 2015
Messages
34
Trophies
0
Age
54
XP
100
Country
Italy
the *only* fact is we have no idea why some people got banned. i'm dipping out of here, see ya next ban wave, bois.

Everyone used an homebrew application in the last N months (or maybe years) has been banned or it will be in the future. If you can still connect online is simply because Nintendo has to carefully check logfiles of several thousand users and be sure to exclude false positives... this takes time but it's just a matter of time. Soon or late if you've used an unauthorized application Nintendo will ban your console.
 

BARNWEY

Well-Known Member
Member
Joined
Oct 11, 2016
Messages
1,268
Trophies
0
XP
648
Country
United States
Woah, so using Freeshop is basically the worst thing you can do (using homebrew while going online). Guess I'll use Wii U USB Helper to download 3DS games from now on. And I'll manually update Luma, FBI, etc.

That's actually a great idea to precautiously use public seeds despite being unbanned. Perfect way to stay safe! :D Do you get those from "that chaos site" or do you have a lesser known source?
Thank you! To get a public seed, just look up localfriendcodeseed_b, and click on the that chaos site link. Go to page 11 for the latest seed...
 
  • Like
Reactions: bjaxx87
D

Deleted User

Guest
Hey guys, after my hard work, now I've successfully analysed 3DS Ticket structure.
I wrote a parser and dumped freeShop's ticket template to see whether some magic exists inside.

Here is result:
============================================================
SIGNATURE:

Type: RSA 2048 with SHA256

Data:

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1

E0A55ED1 E0A55ED1 E0A55ED1 E0A55ED1



TICKET DATA:

Issuer: Root-CA00000003-XS0000000c

ECC Pubkey:

CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE

CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE CEFAEDFE


Version: 0x1

CA CRL Version: 0x0

Signer CRL Version: 0x0

Title Key: ????????????????

Ticket ID: 00000000

Console ID: 00000000

Title ID: aaaaaaaaaaaaaaaa

Ticket Title Version: 0x00

Licence Type: 0x0

KeyY Index: 0

eShop Account ID: 00000000

Audit: 0x1

Limits:

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000



Content Index:

00010014 000000AC 00000014 00010014 00000000 00000028 00000001 00000084

00000084 00030000 00000000 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

FFFFFFFF FFFFFFFF FFFFFFFF 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000


CERTIFICATION CHAIN:

Certificate #0

Signature Type: RSA 2048 with SHA256

Signature:

82798408 346AFD4C CFCA4BEB 12940D1E 9ED43744 1F6660FF B128AB4B D65AFC0F

6D064A9A AF1714A7 81FAAE54 40C906BF 7315BDAA 122F562F 3D52754E 2A737588

67606CFA 9C1C97C8 E2E0130E 7A725CFC 45345D90 996837BF 8D53665A 60786821

4826D7D0 19FEA695 D4123BB2 B9A60C2A EE9D228F 90A6A735 A9FBC893 177995FC

3013A760 88E658FB E0F034E8 C79B67CA D375275A 1380C7C2 26544F1F D1B3471C

9E8DD25C D5A9C1F6 C8DE4631 13F09FB3 94F03210 E4190F2A B2B2CC26 96E39DA7

286D3F38 48ADB80B 9822A002 95404480 C837BFC8 745F0675 C684C28A 9D0787EA

0ABD05C0 3D6896D8 41967850 2EF0A955 CF104988 E7721BCD 52F5D04A 46BE9E91



Issuer: Root-CA00000003

Key Type: RSA 2048

Name: XS0000000c

Unknown Data:

58533030 30303030 30630000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000



RSA 256 Modulus:

25266534 989A8151 F77D5B0C B7282FD1 3D95C697 F8628D0F AC5C6C7C B4E4B678

CD3B18A1 496FB342 C970AC06 C24519AB 093F6C1C 135D1521 62981730 7FE68EDB

34498AAE DDECFCE4 ECB0D365 25F0062A 16B7BC1C AF1249D6 0B8832CD 6166B091

B3DE02A6 670DC5F4 923CB464 EBE9D3E0 5755C3AC E697D978 7A7CE77A FD13DCCC

DCCC6FE3 03A8148F C51239C3 F266174C 2A2DEB9C 85A9CEE9 940459AC E617D0BD

B9FBC621 829962E4 F4AA70EF 81422AA9 36181EF1 133EAAA2 2FA21FEF BE72D010

3EEE6781 B9A228E9 680577AD 1A1889E6 7843B11B 045C9801 268CE926 BBAB4E9F

E2B30B68 11CC7DB7 8885A50D 29CCE972 C710D943 EC3B6ADD 5B2E7EC6 B65B50AD



Public Exponent: 0x00010001

Certificate #1

Signature Type: RSA 4096 with SHA256

Signature:

2E4CCB61 4D6B9094 515E745B D23FCE56 82B010FF 9121F461 868A7D31 E9B70CBC

2443397D 0C55260B 72F2A4E9 A34E35E7 CE565907 6DA30BDB A04077F4 C63EAE90

049A6BAC 515184C1 C93726CD 1EE95750 2395C404 C8106979 7D8E9975 C5D8C83C

7DACA602 155BD58D 9D7A602C 6B09F363 53DC4660 5ED198E7 98DA4E2C 9CFAE516

0DF45413 632BAFFD 458A880B 2F05CD8F D8EDF396 DECB4674 A17771EC F7C1C4B7

CF16C14C 82FD1270 411013D6 DEA2C09B EF184A8E 7E5E9AC6 4640AEF6 52B30296

B94B4FEB D2D96332 30264B33 31854B4A 34821733 1849476F 809C8BD1 836424B9

8868BBAA 8556A5C7 63F419A0 AD68A012 D1954AE1 2120FE78 7E44374A 774AAD1A

7E6F6D16 2C517D57 9B7D2C2E 1F9CC543 88DB997A 1C62910D 44EAD9D9 D1D33287

206ED948 1802C658 EFDBACC9 2A922FD5 9D3C90C2 ECB3AFA9 47145083 8F44A52E

D6B61E51 C18AA1E7 137C505D FCB6068B 62A5C8D4 838946FC 18136B42 54951E57

DAADFF58 8D3DD674 9B645F56 88F6C749 89634078 209283CC E43F0EC3 9F7883CB

5BF7A0EF 95762F07 BF9A775C 5E372234 1B79C8C7 42A2D3D6 BED4E66D 85A13457

A76BD5D6 7BE78CEF B5441CA5 671B41F9 B2B44580 2FA5D9C0 0D9F1E81 033BCB3F

83FF3482 0593A82C 35FE0C6A E3E7A698 6AD759E8 A8969AE8 DD39DC32 100EC57E

23F60EE7 7A5812A3 911B86A2 884C4859 941C6D32 01D97D98 6AA1BDBB EF384170



Issuer: Root

Key Type: RSA 2048

Name: CA00000003

Unknown Data:

43413030 30303030 30330000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000



RSA 256 Modulus:

79D3EEEB 3E9B0134 88AABA14 6D58EF44 CE64EBC3 793562D5 5C916CEA A5618033

2D462F60 63003A07 3BCD698C C0692B83 A44C1520 C7E98DDB 419CD006 6DAF0B20

6DC5BCA2 5E19C70D A6BCF633 BDFF31C4 93823405 708CD29A D3F29954 1FF7A049

D9F90EA6 1BC669CF 51911472 47DE6820 1F11276D 83A12666 0D147F48 AB0DCCE9

20702861 6354991F 0101E99B E06339B8 EAA16305 54F5F035 73CEB8F1 B9847BDD

71D45365 8F1EA9A4 F39FC1D7 1DF663D3 E9332209 E2DA62E5 71F0E7D9 E450DBE2

1DF168C9 5B5298B1 04CC683A B2764697 1DBC601C EFE93AFE 307A3C70 77A11511

72AB550E B5818235 B060959F ED774B8B 078FF839 F64FF4EA C621E1EE E2C979B2



Public Exponent: 0x00010001
==============================================================

freeShop filled lot of junk data in fields marked in red.
freeShop correct fields marked in green during installation.
Maybe this is irrelevant, but I still hope this can be helpful.

The source code and freeShop ticket template binary have attached for research :)
 

Attachments

  • 3ds.zip
    9.3 KB · Views: 117
  • Like
Reactions: nitroBW and TinchoX

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: The Castlevania game was on the PS1 so that's cool +1