Jump to content


Suggestion On How To post direct links for ISO files (or anything) with Mega on forum.

  • Please log in to reply
6 replies to this topic

#1 Mikorist


    ▂ ▃ █ ▅ ▆

  • Advanced user
  • 771 posts
    United Nations

Posted 4 weeks ago

Use 7zip. And encrypt filenames inside an archive. The encryption method AES-256. Use a password to encrypt the files. Encryption will change the hash of the same file and is perfectly undetectable.SPLIT Files..001 files are the format for split files. .001 files are usually numbered as .001, .002, .003, etc. Contain separate parts of a file into Multiple Chunks. In order for a .001 file to work, it must be “joined” back together after download first.

Write in Parameters:


Or in command line version:


7zip then it won't write meta data. So regardless of the created/modified date, the md5 checksum will be same.

Thus, recognition of the raw file hash and file names are foiled (as splited into parts with double AES-256 algorithm encryption).Perhaps God Father can see their contents when they are in parts phase as binary garbage.

Use https://www.base64encode.org/mac, windows, linux, android to make
MEGA Base64 Decode Url and MEGA Base64 Decode Key.

Only this is visible in the post


MEGA Base64 Decode Url: TUVHQSBCYXNlNjQgRGVjb2RlIFVybA==

MEGA Base64 Decode Key: TUVHQSBCYXNlNjQgRGVjb2RlIEtleQ==

Then members can use https://www.base64decode.org/. to decode links.

Credit here goes to 7zip Developer Igor Pavlov and Kim Dotcom.

This is the simplest explanation. I tested this successfully .


Take Down Services are helpless from this.

#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13981 posts
  • Location:The Outside of the Asylum (gate is closed)

Posted 3 weeks ago

I am pretty sure that noone on reboot.pro, particularly if interested on "advanced" topics such as those that are usually discussed here, ever thought of encrypting and splitting files, let alone using BASE64 to code or decode links to them.

Definitely an interesting and new approach, that I am sure will open lots of possibilities, for those willing to distribute software ot more generally data that may be subject to take down notices.

How *any* of what you posted is specifically related to MEGA and what exactly anyone should credit Kim Dotcom for would be however an interesting question. :dubbio:

I thought that he was heavily critical of MEGA:


#3 Mikorist


    ▂ ▃ █ ▅ ▆

  • Advanced user
  • 771 posts
    United Nations

Posted 3 weeks ago

We had hosting problems before.

Because some EXE files from here are considered as a virus.

And then they sent warnings - for removing. Or shutting down the server.

I have no idea how much this can help here (it helps me personally to share whatever I want) .

But that's it.

‘I don’t think your data is safe on Mega anymore’

It's true. But not if I use this method above.

You can actually upload anywhere. Mega is an example :D

#4 Mikorist


    ▂ ▃ █ ▅ ▆

  • Advanced user
  • 771 posts
    United Nations

Posted 3 weeks ago




Use  base64 to decode .


They will never Take Down this  ;) 

#5 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10492 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
    European Union

Posted 3 weeks ago

That's really cool stuff, thank you for sharing.

I used that kind of encryption for sending attachments on gmail accounts that contained binary files. Then recently gmail started blocking them.

With 7zip use this command line to include a password:
7z a -p -mhe=on Directory.7z /path/to/directory
Using your suggestion, it would then look like:
7z a -p -mtm- -mhe=on Directory.7z /path/to/directory

What could preserve the files on the long run is something as IPFS. Albeit this won't solve the issues with takedown notices and blacklisting known hashes.

  • Mikorist likes this

#6 Mikorist


    ▂ ▃ █ ▅ ▆

  • Advanced user
  • 771 posts
    United Nations

Posted 3 weeks ago

7z -v100k a -p -mtm- -mhe=on Directory.7z /path/to/directory
-v100k will split the archive into chunks of 100k.
Directory.7z.001 , Directory.7z.002, etc.
7z -v option supports b k m g (bytes, kilobytes, megabytes, gigabytes)
Only when they are made up of parts is a headache for them. 
They need a billion years to see what's inside  ;) 

  • Nuno Brito likes this

#7 Mikorist


    ▂ ▃ █ ▅ ▆

  • Advanced user
  • 771 posts
    United Nations

Posted 3 weeks ago

More complicated phrase

7z -v100k a -p -mtm- -m0=lzma2 -mx=9 -mfb=64 -md=32m -ms=on -mhe=on Directory.7z /path/to/directory

-v100k Split the archive into chunks of 100k
-mtm- Don't write meta data
-m0=lzma2 Use lzma2 method
-mx=9 Use the '9' level of compression = Ultra
-mfb=64 Use number of fast bytes for LZMA = 64
-md=32m Use a dictionary size = 32 megabytes
-ms=on Solid archive (multi-solid blocks) = on
-mhe=on Enables archive header encryption


Archive and filenames only visible with the use of a passphrase. :) 
7zAES:19 means AES-256 + (2^19) SHA-256 (I have bolded red these points for the sake of clarity).

But ONLY from 
.7z.001 PART ;)
Listing archive: test.7z.002
ERROR: test.7z.002 : Can not open the file as archive :D


Gmail don't have a clue what is .001 mean and what's inside. As well all other scanners in the world.


Because they are a bunch of binary garbage  visible as a random flicker of "dots" or "snow"





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users