dustine / dragencrypt-winforms

Software toy to easily encrypt/decrypt Windows files, password-based

#DragEncrypt A simple programming toy that encrypts and/or decrypts any files that are dragged to it with an user-chosen password key.

##How to Use Drag any binary file into the executable file. Simply opening the executable will open a file dialogue prompt as an alternative method to pick the targeted file.

A window will appear where the user can insert the desired password, with a holdable button to peek into it.

Decryption is done with the same method as encrypting, just requiring the encrypted file to be the chosen target.

##Safety concerts The program takes no extra security precautions during its run, beyond trying to delete the unecrypted password 'quickly', so the process is rather vulnerable to attacks before and during encryption, likewise for decryption. However the created encrypted file should be mostly safe from brute-force attacks or re-engineering, or at least as safe as the chosen password.

##Contributing

This software contains icons from the WPZOOM Developer Icon Set (WPZOOM) / CC BY-SA 3.0.

dragencrypt-winforms's Issues

Lack of Unit tests for Core

Having proper versioning control for internal cryptography algorithms (aka backwards compatibility)

The version field in the encrypted file's header is just fluff for now, whatever the version the algorithm that is run is always the same. (At least it's better than before, now it at least takes into account the encryption and hashing techniques detailed in said header).
This shouldn't be the case. Changing it implies using the rather abandoned IDecryptionAlgorithm interface. I think.

Folders should be able to be encrypted and decrypted as well

As an alternative solution to #1, allowing folders to be encrypted just like any file.
Possible method would be to:

1. Zip the folder (Gzip)
2. Encrypt the obtained file, as normal
   • But have a special header to indicate it being a folder
3. Have decryption picking it being a folder automagically.

Securing the meta-data and its contents more rigidly

Speaking particularly of the IV and Salt in the header. They're just saved as plain--text--data, which may be ill-advised.

Actually decent and user friendly exception handling

I have no excuse for this beyond laziness.

System.UnauthorizedAccessException when trying to encrypt a folder

Only crashes after the encryption takes hold, which should not be the case. Shouldn't allow folders to be selectable at all.

Giving use to the progress bar

It's there in the interface, right behind the action button, doing nothing. The code for using it is commented somewhere, the issue is tracking the relative progress without mucking the used streams. So it's either that, being ingenious or removing it.

Dragging files into the main window should put them for decryption/encryption

Just a way to ease way of use (and it makes sense, it still IS a drag&drop action)

Lack of Unit tests on TempFileGenerator

As, per example, to see if the files created by it possess the FileAttributes.Temporary attribute.