[Feature request] How to know I'm seeing encrypted drive when using plaintext filenames

Pgr

Hi,

I use Boxcryptor with plaintext filenames (to make it easier to recover previous versions from Dropbox).

This can be confusing (especially for less technical users I share folders with) because the two different views to that folder look just the same: if I go through Dropbox I get encrypted files, if I go through the Boxcryptor drive I see them as normal files.

But, as I said, there is no apparent difference until I click on a PDF, for example, and get a message saying it's corrupted. People can panic at messages like these...

Right now I use a text file called "Test Me.txt" that contains a few lines of text, and people can use it to confirm which view they're looking at: if the contents appear garbled, it's the encrypted view.

My suggestion is for you to study what is the best way to handle this doubt properly.

Perhaps an option to use plaintext filenames, but with a different extension: for example, a file called readme.txt could be saved encrypted as readme.txt.boxcrypted. You could register this .boxcrypted extension to show an explanatory error message when a user tries to open an encrypted file, and even let him proceed with opening after providing the password.

Thank you for a great program!

Robert

Hi,

we're aware of this problem and when you're creating a new BoxCryptor Folder we already create a .txt file called "!IMPORTANT BoxCryptor Information.txt" which is not shown in the BoxCryptor Drive.

Of course, we're also thinking about better solutions for this problem for the future.

Best,
Robert

Pgr

Funny, I never saw that file called "!IMPORTANT BoxCryptor Information.txt"... calling people's attention is not an easy thing these days... :-)

I'll be waiting for your "better solution". Thanks!

CC

Please do not introduce a filename extension, and certainly not a fixed one.

If you really think adding a filename extension is the only solution for some BC users, please let users at least determine whether 1) an extension should be used at all or 2) what the extension should be when a boxcryptor drive is created.

Many tools, command line based and others, provide an option to specify a filename extension by end-users, if extensions are somehow required.

Quite some people ( other tool forums / discussions ) want to define their own extension, and in case of encryption tools, they even appreciate to choose an extension from which it's not clear to others that particular directory trees are encrypted ;-)