[miso]

Im creating a completly new filetype to prevent my future tools to be edited by users to make them malicious, even though i like having things easily editable, i'd really like to keep other stuff to myself, hence why im making this filetype.

This filetype brings:
- Image-Signed Encryption (meaning the key will be an image)
- Nothing will be extracted as files (everything will be handled in memory)
- Dumping Protection (the "protected" application will still need to be manually obfuscated)

most of my tools uses the .NET Framework, but i might post other stuff such as in X++, even though it is very unlikely.

I will release a decryptor soon but no encryptor, if you want to encrypt your application, you will need to PM me.

Edit: you can propose your own one if you want

[Drako]

.msly is my personal favorite. A solid acronym combining your name and the forum's name.

[Dismas]

I'd go with .miso if you want something personal. If you want something to represent the site .sl or .sly (if those aren't already existent).

[miso]

I'd go with .miso if you want something personal. If you want something to represent the site .sl or .sly  (if those aren't already existent).

.miso sounds like an alternative to .iso, after idk, ill see what others have to say ^^

[mothered]

Im creating a completly new filetype to prevent my future tools to be edited by users

Your Intention should fit the denotation of the file type, so my answer Is obvious: .pt

[miso]

Im creating a completly new filetype to prevent my future tools to be edited by users

Your Intention should fit the denotation of the file type, so my answer Is obvious:  .pt

well true, however i find it a bit blend, it would fit more for a basic protector

[mothered]

Im creating a completly new filetype to prevent my future tools to be edited by users

Your Intention should fit the denotation of the file type, so my answer Is obvious:  .pt

well true, however i find it a bit blend, it would fit more for a basic protector

All In all, you're protecting your files, Irrespective of their nature.

[Mr.Kurd]

This is kind of Personal and Also representing SL but for personal files so am saying .msly is the perfect one.

[miso]

Thanks for everyone that voted on the poll, the file type will be named ".msly"

i however have a question, which is how should i pack applications that have dlls included, the current packer only support a single file. I think about using a zip with a password using a long password (the techinique of how the password is going to get created will not be explained), then when the msly is asked to load, it will unpack itself in memory.

the filetype contains numerous checksums to make sure it is a valid file, it also has a version number, if it does not correspond, you will need to update the loader (updates are not supposed to happen frequently, and will most likely be retro-compatible with older version of the msly filetype. (meaning you cant load a version 1.1 msly with a 1.0 reader, but a 1.1 reader can load both 1.0 & 1.1 msly versions)

PS: the msly loaders might be a big target of false-positives on virus scans due to the numerous memory instrustion aswell as decryption. The filetype will most likely not be able to get scanned via virustotal, so i might want to do seperate tool for that.