Here's some important links you might want to check out! My Discord: discord.gg/rY4unvn RetroGamingNow Discord: discord.gg/retrogamingnow Tominecon.7z Team Discord: discord.gg/Q2BU69AN3S Download tominecon.7z: buu.sh/u/tominecon.7z
@@_Ecliptic and that's probably ceiled, and even if it wasn't, that must be rounded so if it's rounded it would take 1 second to 0.5 SECONDS. yet with like 100 passwords, and at least 1 TOP (trillions of operations per second), it WOULD take less than 0.1... like, c'mon! Just how! Computers are so advanced it's hard to fathom. And now I made a long comment for no reason
@@decoy3211 I was born in 2001, on the 12th of April. I am 23 years old. My RU-vid account also states it was made in September of 2012. It's extremely unlikely I would have made a YT account at 5 years old.
It's also all wrong... Minecraft didn't have encryption for client server communication until snapshot 12w17a (For version 1.3.1) after the Netty rewrite! This part of the client hello packet was only used for authentication.
Also, Long.parseLong will just throw a NumberFormatException if the String that's to be parsed contains letters outside of the radix. So you probably wouldn't even be able to connect in the first place I think.
Well yeah, the data is still encrypted, just the wrong way, so it "breaks" the process of encrypting the data on the server end and decrypting it on the client end. I'm not a professional at encryption by any means - this was just how I made sense of the process in my head and I wanted to explain it briefly, so it may not be 100% accurate
Lol, RU-vid algorithm works that way I guess. On videos talking about how good something is, I often get recommended videos talking about how bad it is too
@@MaakaSakuranbo because having a poorly informed passwords list makes it exponentially less likely to crack via brute force. brute force methods with modern encryption do not attempt every possible character combination possible, that would take billions of years. cracking things is often far more successful with some level of research or enumeration.
@@MaakaSakuranbo surprisingly even simple passwords can be hard to crack if they're not in major wordlists. the research used to crack the tominecon.7z archive was simply that there was already a pre-existing list of cracked mojang passwords, that only certain people would have had access to. (particularly those who hack minecraft accounts because of their unique names).
great video! the only thing missing here is a mention that the server files are in fact different builds from the final 1.0.0. while code-wise (and even content-wise) they're identical, the final 1.0.0 server was built 6 hours after the tominecon 1.0.0 server, making them have different file hashes.
10:15 No, parseInt would just throw an exception, which would then be caught by the try-catch blocks surrounding that code, which would then disconnect. I don't even think the serverid is used for encryption, but if it is, the encryption wouldn't be "broken", it'd just fail to decrypt/encrypt anything because the keys don't match up.
Yeah, which on the client-side means multiplayer doesn't function at all since you're disconnected before you ever get into the server. Server ID is used during the encryption process, but not to actually encrypt anything itself, just as data that gets encrypted sent to the client to allow the client to start decrypting the info and play the server
GGs to Doge who somehow decided to keep the old leaked passwords, then to Dinnerbone who helped have this spread further, and of course, the original user who had sent the real thing and not a decoy.
That explanation about encryption is.... entirely wrong. The parts about hex and dec are correct, but everything else is completely off the mark. 1. The server only ever sends _encrypted_ data. Your client only ever sends _encrypted_ data. There is no way for the game to do anything else, _by design_ . It would be a massive security risk if the opposite were the case, not only for your account details, but both your computer _and_ the server machine. 2. There is no way for encryption to "break" and be left completely open while in transit. That's not how encryption works, unless someone very stupid implements a fallback to plaintext which defeats the point of encrypting that data in the first place, as you could just force one side or the other to fail, receiving all that data without needing to decrypt it. 3. The server ID being parsed in the wrong base wouldn't initially cause an issue. In fact, you'd be able to _try_ to connect just fine. You wouldn't be able to fully connect, but you could try. 4. The reason it appears that multiplayer is completely disabled is because of a related (but different) problem. The first time the server (or your client, on modern versions it's the client) would try to send a packet the other would receive, what appears to them as, a garbled mess of incorrectly encrypted data. As such, they'd immediately close the connection, since trying to proceed would be a waste of time. The decryption fails because the encryption keys (in this case, the server id) would be different on either end, like trying to log in with the wrong password.
1. Yes, that's what I'm saying. I said it would be a huge security risk if it let you send the data unencrypted, so instead, it fails to encrypt your data and multiplayer doesn't function. 2. I didn't mean it would unencrypt the data and send it, just that, well, it breaks the encryption, it makes the whole "sending encrypted data" process not function properly. The visual does make it seem more like it actually sends unencrypted data though, I admit. I wasn't really sure how else to visualize that for someone who's not familiar with encryption, which includes most people that have watched this video so far. 3. Also what I tried to say in the video, though maybe I explained it poorly. Connecting to any servers on 1.0 immediately fails. You can enter the IP and press enter, yes, but it never will connect you. 4. Possibly, yeah. I don't know the process for this super well - I was mostly focused on the process of discovering the file, and just wanted to briefly touch on why the difference between 1.0 and tominecon is so important.
@@mcbyt Sorry if that sounded harsh, I did enjoy the video - I'm a CS nerd at heart so the inaccuracy rubbed me the wrong way lol Just about everything to do with encryption is hard to explain, so kudos for giving it a shot :)
@@TheKd8lvt All good (sorry I didn't see this till just now)! I appreciate being held accountable for stuff like this, I never want to be putting the wrong info in videos ofc :)
The fact that it was broken in such a simple way without some expert cia level shit like that methods, along with the only difference of it between the offical 1.0 being 4 characters in the code feels so anticlimactically funny
3:36 Oh my God, I just love seeing other RU-vidrs I watch being mentioned in videos, this mystery would have gone in a very different direction if any of you didn't cover it! From the seeds of panoramas, to paintings, now passwords to files.
10:16 no, the data would be encrypted, the encrypted data just wouldn't be able to be read by the server since it didn't have the right decryption key. this would cause the client to be disconnected. also, passwords aren't sent to the server, your Mojang session ID was sent to the server. sending your password unhashed to an unofficial server is a huge no-no.
Pls stop the clickbait, it's not a "great mystery" or "some mystical code", is just Minecraft 1.0 in password-protected archive with a lame password. A great mystery would be if someone reverse-engeneered the Minecraft binaries and found some advanced and complicated code that send encrypted data to Mojang servers for example. That would 100x more interesting than this nonsense.
well that's not a mystery, that's the truth? It's called analytics and when Microsoft bought they introduced more intrusive logging which you weren't able to disable (I think that changed since then)
would personally never have guessed the password to be 6 letters and 2 numbers, one would think that would’ve shown up in people’s dictionary attacks by now
9:37 : it's not a "server id", it's an encryption key. the code literally says right there that if it fails to parse the "server id" it will stop and say "The server responded with an invalid server key". 10:09 : no, it couldn't. of course it couldn't. where in the world did you get that idea from? right in the oracle docs: Throws: NumberFormatException - if the String does not contain a parsable long. 10:13 : wrong again, the code says right there that if it fails to parse the "server id" it will stop and say "The server responded with an invalid server key". even if it *did* try to communicate without the right key, all of the data between the server and client would be garbled and a connection would never be established. did you run this section by someone who knows anything?
The mystery is not about what was in the file. It was about the process and the excitement of finally answering one of Minecraft most asked questions. You witnessed history. Be proud.
Less so the content of the file, moreso the hunt to crack it like albert said. I mean, there's been millions of eyes on this random file for over a decade now!
The fact we not only cracked the password but learned TONS of stuff about the files is nuts. First, the contents of the file, and the fact it IS different from an actual release of 1.0 Minecraft- albeit very, VERY slightly. And yet that slight change was such a massive problem... quite interesting, honestly. Second, the password, which is amusingly only 8 characters long... go figure. No wonder they were so worried about the password... in fact, using the password strength checker shown earlier in the video, the password for the original file is WEAKER than the password for the decoy! Third, the two things the password was used for. Since it was originally for their email account, it makes sense why it was so worrying. But with that changed, it's a lot safer now. Dinnerbone wasn't kidding when he said that. And fourth, the fact that when many people are curious, nothing can stop them. This was probably the craziest thing that could have happened... but I'm glad that there's finally a concrete end to this saga. (Let's not go trying to crack any more files unless given advance knowledge that it's for an ARG or something.)
Yeah… I can see why no one wanted the password out there in the early days of the hunt (Even the people who claimed to have cracked the password said they probably shouldn’t have done it) if it was the making email password
I can offer a lesser rant XD - there is a password protected zip in the minecraft files - mojang magically finds out about people trying to crack the password, I guess the zip was sending them signals in dreams - lie about how 'boxpig41' password took 10 years to break when in reality it's only 50 minutes with a bruteforce - mojang replaces it with a false zip - 2 other channels trying to leech viewership comes on the story (you know, you could speak about the actual people that cracked it and not a youtube channel handle) - 1 of them has the original file and password finally get cracked (guess they chose to use the 50 minutes brute force this time) - the zip has the same files but with just a parameter missing in one of the functions that is supposed to turn a string to hexadecimal format as if the string FORMAT was the one keeping packet sniffing away and not the ACTUAL string ITSELF
Mojang could probably tell by the constant discussion of this on HackForums and Reddit, this is extremely likely. Explanation he gave here makes sense. Also the password was apparently found by credential stuffing, which, as seen in hashcat on the video, took one second. Also yes the string format requires the string itself to be correct. If the string format is flawed the server wouldn't be able to understand the traffic - however there would be no interesting data that anyone would/could listen to, as it'd just be a "hello?" and the server disconnecting you, or you disconnecting. Whichever comes first
But there are a few other questions, for example when you are in .minecraft/bin, there is a file that contains all the md5 hashes of the .jar files First, this file mentions a file called windows_natives.jar.lzma, which I couldn't find Second, all hashes match the hash of the file, except for minecraft.jar
Minecraft.jar doesn't match because that's the modified file I discussed in the video. Not sure what you mean about the windows natives jar or where that's mentioned - if you mean it's in the code of Minecraft.jar, then it's probably elsewhere in the 1.0 files or possibly something that's located in Windows itself.
The md5 hashes are in the tominecon File at .minecraft/bin. In this File is a Line which refferenced in a windows_natives.jar.lzma file I will Check later If the Hash mached the original Minecraft version
hey thanks for this video this is super cool! im part of the RGN community and thought it was cool that you were the one who kinda was behind it popping up again!
to be honest the devs literally said to not crack it, along with some other people, the fact that no one even bothered to listen to them just shows that they won't listen to the community when they do something wrong, we didn't listen, why should they?
Your characterization of the int parsing bug isn't really accurate, or at the very least *very* sensationalized. There wouldn't be any significant security issues.
this channel is just consistently good like seriously the amount of stuff that minecraft has undiscovered that you somehow find about and make thousands also be interested in is crazy
I thought it was weird how RGN tried to imply that it was impossible to crack in his follow up videos after the first video blew up. I mean, weirder and more difficult things have been achieved before. It seemed like a matter of time and boy that was fast
in rgb first episode, he said that there was someone who cracked it on the hacker forums, and that guy also said that if it went to wrong hands, it would cause a catastrophe. With this video it now supports his claim, he most definitely investigated the file and found the decimal format you talked about.
The decimal issue would have thrown a NumberFromatException (an error) if the number it got contained digits that it doesn't know, so in no way shape or form would it have caused a catastrophe, it would probably have kicked you out with an error the instant you tried to connect to a server because of it.
I don't think so. The file going public wouldn't be a catastrophe at all, it'd just be really bad if Mojang released it officially. A buggy 1.0 build doesn't cause problems if it's leaked, only if it gets an official release as Minecraft's most important version of all time and millions of players are disappointed by its broken multiplayer
such chill folks at mojang. and the interesting part is that, while the skills and methods may have malicious applications, by publically stating and engaging with the process they effectively give permission for users to try. as if its a challenge to them. ergo, while the tools may potentially be questionable, the act is not considered in violation of the law than if you added a randomised password to an empty file and then tried to get into it. it goes from an illegal act to one of grey legality.
10:15 that’s a ridiculous statement to make. If you’re correct and the server ID is “used” to encrypt data (which is probably a stupid and insecure idea anyway), that would mean it’s the encryption key. Worst case scenario your game / server crashes from failing to encrypt data to send or failing to decrypt data that was received. Either you pulled that last part out of your ass, or old Minecraft servers use some really weird non standard method of encryption you’re somehow aware of
“Hey can I copy your homework?” “Sure but just change it a bit.” Talking about how this video’s thumbnail and title is IDENTICAL to the other video you made
@@susguy187also there’s no 1.0 servers anyways because they’re either 1.8/1.7.10 or they’re the latest version No server uses 1.0 anyways so like the version still works it’s just multiplayer like single player works
