If you've installed Launcher v0.7b12, then you already know that I'm working on File Cryptor, also I'm slowly working on Clipboard Inspector and CheckSum tools. I'll explain what
are those and we'll move to my main work related to v0.7c.
File Cryptor - a basic tool that can securely encrypt/decrypt any file. The UI is rather simple - 2 fields for passwords of any length and complexity + button to encrypt + button to decrypt.
What would be the use case for it? - /whatever you want, for example You enter both of the passwords press encrypt, then send your file to your friend using any file sharing site, messenger or whatever and give him passwords through some other messenger or 2 other messengers or whatever other way, making it nearly impossible for 3rd party to get a peek on what you were sending over, unless they can get their hands on all of the required stuff (e.g. file + 1 password + 2 password). Or you can store your secret files on your PC in this way, just don't forget your passwords
How secure is it? I won't disclose all of the backstage in this post, nor in the future posts, nor in the File Cryptor description, so that it will be even more secure. First of all those 2 passwords are not the only thing that is used to encrypt the file, moreover even with exactly same file and exactly same passwords each encryption will result in a unique file, so in order to have any descent chance at decrypting the file, the person that will want to do so will firstly need to figure out that it was produced by Launcher, so that he/she can crack Launcher in order to lookup the encryption method, otherwise the chance of figuring out what method was used in encryption is extremely small. Launcher actually does add a special extension to encrypted file, for the ease of use, so that actually is a kind of trace, but you can simply rename it to any other extension to remove that trace + you can encrypt over and over again multiple times if you're super paranoid
.
Let's imagine that a person with malicious intent somehow figured out that it was created via Launcher and cracked Launcher, will it be easier to decrypt the file with such knowledge? Of course it will be easier - now it all narrows down to your passwords, that said - this person won't be able to figure out what that file is before decrypting it, which will require a great computational force if you used a descent passwords, so unless they have one of the supercomputers (at which point you should be worried about something else, and you should've encrypted it over and over again multiple times with different passwords in the first place), that's probably not going to happen any time soon. In other words - decently secure.
I have a perfectly working implementation of it for files below 3.something GB, currently figuring out a good way to overcome certain limitations + overcome limitations of small RAM size for a huge files, if I won't figure that out in some near future then I might impose hardcoded limitation to 3GB max and release it as it is now, we will see. The reason why I'm not releasing it as it is now - you won't be able to decrypt older files when the improved version will appear.
More options and various encryption methods might be added in the future.
Clipboard Inspector - a rather straightforward name, an inspector of Windows clipboard. The functionality for it will be added over time, and I'm not sure what will be added at its release yet. Few things that will definitely appear at some point in time - check out what's inside Clipboard at this point in time, clear Clipboard, and the main feature - check which programs read Clipboard (can be used to detect if there's any suspicious program reading your clipboard content), also I might add "Clipboard history", but not entirely sure about that one yet.
CheckSum - checksum of a file and probably a text as well. At start I'll add SHA1, SHA256, SHA384, SHA512, MD5, CRC32, CRC64, elf32, RIPEMD160 (already implemented those). A whole lot more will be added in the future. UI is still a subject of consideration, so if you have any suggestions - feel free to post those.
And finally moving to the main work on v0.7c - External FEX is almost finished, I just need to add refresh of the advanced tab UI related to it (other than that it works fine, just requires Launcher restart at this point in time) and check if I haven't missed anything with other servers, as obviously I'm testing it only on JP one. Once that will be done I might release it as v0.7bXX if anyone will ask for it.
Meanwhile here's an example of External FEX:
Code: Select all
{
"FEX": {
"JP": {
"JP Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01_japan.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01_japan.dds",
"SupportedStyles": "Force"
},
"KR Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01.dds",
"SupportedStyles": "Force"
},
"EU/NA Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01_northamerica.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01_northamerica.dds",
"SupportedStyles": "Force"
},
"RU Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01_russia.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01_russia.dds",
"SupportedStyles": "Force"
},
"TW Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01_taiwan.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01_taiwan.dds",
"SupportedStyles": "Force"
},
"SA Watermark": {
"PackedFileName": "ui_texture/new_ui_common_forlua/widget/watermark/screenshot_watermark01_southamerica.dds",
"RAWDestinationFileName": "\\ui_texture\\new_ui_common_forlua\\widget\\watermark\\screenshot_watermark01_southamerica.dds",
"SupportedStyles": "Force"
}
}
}
}
JP - server name (default External FEX will ship with examples for all of the servers out there).
JP Watermark - your /whatever name that will appear in advanced tab, and will be used via Projects, so make sure that every one of those are unique.
PackedFileName - destination used by the game client (more on that later).
RAWDestinationFileName - where the file will be extracted (it starts from Launcher\BDO\RAW\ServerName"Here goes your path").
SupportedStyles - supported patching methods (None, Safe, Force. E.g. in order to forcepatch you'll need to specify Force).
That is probably everything for now.