[Suggestion] Encrypt files in a folder individually instead of packing the folder into a zip package.

[Asudox]

I think a option to encrypt files individually and recursively could be useful for some.

[HACKERALERT]

Yeah this has been requested multiple times in the past, to which I have said no. But it looks like a lot of people want this feature, so I think I will give it a go. I'm busy at the moment so it may take a while to implement, but I'll keep this issue open until then.

[Asudox]

Alright, good to know.

10. Apr. 2023, 21:01 von @.***:

Yeah this has been requested multiple times in the past, to which I have said no. But it looks like a lot of people want this feature, so I think I will give it a go. I'm busy at the moment so it may take a while to implement, but I'll keep this issue open until then.

—

[HACKERALERT]

In a spark of motivation, I've added a (simple) CLI to Picocrypt! It should allow you to encrypt your files however you want, including separately and recursively. Let me know if this is a "good enough" solution for this specific use case!

https://github.com/HACKERALERT/Picocrypt/tree/main/cli

[Asudox]

In a spark of motivation, I've added a (simple) CLI to Picocrypt! It should allow you to encrypt your files however you want, including separately and recursively. Let me know if this is a "good enough" solution for this specific use case!

https://github.com/HACKERALERT/Picocrypt/tree/main/cli

Uh yeah, but I have no idea how the recursive file encryption would work, the only usage example it gives me is: picocrypt -p password <file>

And even then, there's a checking done in the main.go file:

if stat, _ := os.Stat(filename); stat.IsDir() {
    fmt.Println("Directories are not supported.")

I don't know Go, but I am sure I understand what this if statement does. So how can I recursively encrypt files if directories are not supported?

[HACKERALERT]

Yeah the CLI is meant to only work with one file. What I meant was that you can then use a script to encrypt however you want. For example, on Windows, you can do something like this to encrypt all PDFs in a folder:

for %f in (*.pdf) do picocrypt -p password "%f"

[Asudox]

Yeah the CLI is meant to only work with one file. What I meant was that you can then use a script to encrypt however you want. For example, on Windows, you can do something like this to encrypt all PDFs in a folder:

for %f in (*.pdf) do picocrypt -p password "%f"

Oh, I see. Thanks. Then I will be closing this issue as it seems good enough to me. Don't know about the others though. You might want to consider adding it to the GUI someday. Goodbye.

[HACKERALERT]

The GUI is a bit clogged and busy already, so I would prefer not to make it more confusing lol. Most people won't need to encrypt recursively, and for the people who do, they probably have some scripting capabilities and will be able to use a CLI. I think it's a good compromise :) Thanks for bringing this to my attention!

[Minibus93]

Sorry to re open this, as I just read it.

Personally I'd say this feauture is important enough to be definitely worth of a spot in the GUI IF this will be the go-to way to encrypt files however the user wants.

I see this requested since ages and relegating it to CLI just doesn't seem to serve justice (unless CLI only is a temporary solution)

Just my 2 cents

[HACKERALERT]

That's fair. The one thing that bothers me is when I add a "Recursively" checkbox to the UI, now there's an empty space for another checkbox that's unfilled and looks rather ugly. Although I think if I add "Deniability" as well, I'll kill two birds with one stone -- add the recursive encryption option as well as adding a plausible deniability option which seems to be a important feature in today's world. It'll take a while to make these two features, but I'm willing to spend some time and effort to make Picocrypt the go-to tool, as always. Let me know if you think these two features will finally make Picocrypt "complete". Thanks!

[Asudox]

That's fair. The one thing that bothers me is when I add a "Recursively" checkbox to the UI, now there's an empty space for another checkbox that's unfilled and looks rather ugly. Although I think if I add "Deniability" as well, I'll kill two birds with one stone -- add the recursive encryption option as well as adding a plausible deniability option which seems to be a important feature in today's world. It'll take a while to make these two features, but I'm willing to spend some time and effort to make Picocrypt the go-to tool, as always. Let me know if you think these two features will finally make Picocrypt "complete". Thanks!

I am sure, for the time being at least, the features included right now and the little features you might add in the future would be plenty enough for Picocrypt, it is supposed to be lightweight so people wouldn't expect a feature filled software. Albeit I see the option to be able to encrypt files recursively a very important aspect in encryption software. For example, I needed the recursive option to encrypt my USB devices, as I don't have Windows Pro, I don't have BitLocker, thus I can't encrypt my USB device. The other software aren't right. A small go-to encryption tool like this that can stay in the USB at all time with minimum space compromise is what I need - which literally is Picocrypt. Now the CLI can encrypt "recursively" using a for loop in Powershell but to be able to just do it right in the GUI is surely more convenient. I'll be sure to have the CLI as a backup though.

[HACKERALERT]

Closing in favour of #154.