search

HACKERALERT / Picocrypt

A very small, very simple, yet very secure encryption tool.
GNU General Public License v3.0
2.42k stars 145 forks source link

Unable to decrypt file with no .pcv extension #162

Closed hakavlad closed 1 year ago

hakavlad commented 1 year ago

For example, random.bin is picocrypt encrypted file (with deniability). I dropped this file in picocrypt window and picocrypt suggests only Encrypt mode. I'd like to decrypt the file without renaming.

BigPanda97 commented 1 year ago

How should it detect that the file is encrypted without the extension when using the "deniability" feature? 🤦🏻‍♂️

hakavlad commented 1 year ago

How should it detect that the file is encrypted without the extension when using the "deniability" feature? 🤦🏻‍♂️

The user knows what the file is and must have two options - decrypt the file and encrypt the file. The standard extension is a bug, especially in the case of "deniable encryption" .

HACKERALERT commented 1 year ago

Adding both an encrypt and decrypt option is redundant. If you drop in a file without .pcv, 99% of the time the user wants to encrypt it. For the other 1%, I think it's reasonable to just add an extension, since as you mentioned, the user knows it's a deniable volume, and decrypt it. Ideally people shouldn't ever need to use deniability, so it's best to keep Picocrypt clean and simple for the majority of users who don't use it.

On Sat, Jun 3, 2023, 8:46 a.m. Alexey Avramov @.***> wrote:

How should it detect that the file is encrypted without the extension when using the "deniability" feature? 🤦🏻‍♂️

The user knows what the file is and must have two options - decrypt the file and encrypt the file. The standard extension is a bug, especially in the case of "deniable encryption" .

— Reply to this email directly, view it on GitHub https://github.com/HACKERALERT/Picocrypt/issues/162#issuecomment-1574925437, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALUMDTDVK4AXPGA2WPCJSDDXJMW2FANCNFSM6AAAAAAYZHPEPM . You are receiving this because you are subscribed to this thread.Message ID: @.***>

HACKERALERT commented 1 year ago

Also, the standard .pcv extension for a deniable volume is not a bug. People who need to use deniability will likely be smart enough to know to rename the output file after encryption. So I'll leave that part to them because if I choose a custom extension such as .bin instead, it's likely the user will want to rename it again to suit their use case.

On Sat, Jun 3, 2023, 8:46 a.m. Alexey Avramov @.***> wrote:

How should it detect that the file is encrypted without the extension when using the "deniability" feature? 🤦🏻‍♂️

The user knows what the file is and must have two options - decrypt the file and encrypt the file. The standard extension is a bug, especially in the case of "deniable encryption" .

— Reply to this email directly, view it on GitHub https://github.com/HACKERALERT/Picocrypt/issues/162#issuecomment-1574925437, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALUMDTDVK4AXPGA2WPCJSDDXJMW2FANCNFSM6AAAAAAYZHPEPM . You are receiving this because you are subscribed to this thread.Message ID: @.***>

hakavlad commented 1 year ago

OK