There’s More To The Minecraft Code No One Has Solved

It's worth noting that the password may be a phrase or combination of words in Swedish, or involve character names from fiction.

Most popular wordlists for crackers are taken from databreaches for english-speaking services, and while most of the 2011 Mojangstas speak fluent english, it's not their native tongue.

Additionally, this factoid can make even simple passwords completely inaccessible to typical brute force attempts, since the program may not be accounting for Å/å, Ä/ä, and Ö/ö.

Was fun to watch.

Great video! It was really well made and interesting! The only problem was how long you spent talking about the number of possible passwords to other big numbers lol
Still, wonderful video!

Hello Retro, I really enjoy watching your Minecraft lore videos, and the last two have especially caught my attention. I am a Computer Science student at UCO, and I just completed a Cybersecurity course for the Spring semester. I wanted to chime in regarding AES encryption while the information is still fresh in my brain.

AES is a block cipher, meaning it will encrypt an entire block of data at a single time. The block size is always 16 bytes, or 128 bits. The default mode of AES (ECB, or Electronic Code Book) has a specific weakness where identical plaintext blocks will produce identical ciphertext blocks. This is due to the same, unchanged, key being used to encrypt each block. This means that if the file is encrypted using ECB mode, the overall pattern in the data will be easily visible even without needing to decrypt.

There are a few other modes of operation used with AES, each of which require something called an Initialization Vector (IV). This is a random number that ensures blocks will produce different ciphertext regardless if they have identical plaintext. The IV has a fixed size of 128 bits (same as block size), which means it has 2^128 different possibilities. This means that if the file is encrypted using any mode other than ECB, you would need to guess not only the key, but the IV as well, leading to a calculation requirement of 2^128 * 2^256 (depending on the key size). If the IV generator is predictable, you can easily guess it but you would need multiple messages to see a pattern in the IV generation, and since this is a single file that is not an option. Overall the computation requirement would be around 2^384 to brute force an AES-256 encrypted file that was encrypted using a mode of operation including an initialization vector.

I hope I could provide something you didn't previously know and these past two videos have been super interesting to me! I love being able to share knowledge from school so it doesn't just go to waste!

P.S. If you use Linux and read the file in hexadecimal format, you could probably pick out a pattern pretty easily if encryption was done using AES-256-ECB!

I think it’s a version of Minecraft that could have source code or removed features that’s why it was tooken down

The idea of someone suggesting "just break the AES-256 encryption" as a solution is up there with Q suggesting "just change the gravitational constant of the Universe" as insane overkill solutions

solution: travel back in time to when notch (or whoever else) made the file and peer over their shoulder

1hr ago
7am
Fri 17 may 2024
+4gmt

I think people underestimate how sloooooooow the 7Zip encryption algorithm is. it's not MD5, it takes FOREVER to brute force (mostly on purpose). until quantum computers reach the point of cracking AES-256, there is no way we'll ever see the contents of this file if the password is even remotely secure

How about a distributed network of hundred of computers to brute force it lol

Edit: I understand and even expect all the swear passwords, lol. It was "cheese," "monkey," and "dragon" that made me laugh.

I think you should start teaching badic computer science stuff, haha. I'd always wanted to learn things like that, but my brain is wired completely for artistic things, so I have a lot of trouble grasping some concepts.

You make some really easy-to-understand analogies and quantify the concepts so that people like me can finally begin to understand it.

I know that probably sounds super boring, but just throwing it out there. I think you'd make an amazing teacher. I'm talking just basic ideas and things, like you've demostrated in these videos. You can even use analogies related to Minecraft and such. 😊

The trick to reducing the possible number of passwords is to try to figure out who chose the password and try to get information about them. If we assume it's a numeric password as the false lead said, you might try combinations of dates important to the person or organization. This is why social media scammers and social engineers will try to find personal information about you like pet names, names of family members, et cetera. If they can figure out some information you're likely to use in a password that provides a range of possibilities they can try before they result to brute force.

We need Kamala Khan to crack the code.

I wis i knew it

5:42 I really enjoyed the first video, but this whole number thing was just filler my dude. Could have been a 20 second thing with the same impact.

Just mine the password like Bitcoin.