+[8.50.b3]RAR: TC checks automaticly 'Encrypt' while packing

[Biozynotiker]

TC automaticly adds/checks the "Encrypt" option,
if there is at least one encrypted file in the archive,
while adding new files to existing archive.

(I'll test this with rar5 container, can't test this currently with rar4.)


EDIT:
I overlooked in the history.txt, that this is a new "feature".
Please make this optional, that makes absolutely no sense!
If you have archives with several 10.000 files, and even 1 files is encryted,
TC bugging the user to encrypt all new files.

[ghisler(Author)]

This is not a bug, it's intentional so you don't add unprotected files by accident to an archive containing protected files. If you don't want it, you can simply press ENTER in the password dialog, and the file will be added unencrypted.

[Biozynotiker]

Seriously? Pressing Enter/Passing Password dialog everytime I add a new file?
Think about twice, so you can't use passwort manager in a useful manner.

So, 8.01 is the last useable version after nearly 20 years of using TC.
This is a absolute showstopper.

Bye Bye TC.

[ghisler(Author)]

Why do you want to mix encrypted and unencrypted in the same archive anyway? That's a very bad idea for security.

[Biozynotiker]

There is alot reasons for mixing normal and encrypted files. 2 Examples:
Using a archive like "documents.rar", this can contains some manuals
or some scanned documents thats worth to protect for curious eyes.
You can archive many different software in one archive and only
protect the licence file, so co-workers can do their jobs, but have to ask
for passwords if needed etc.

You don't have to split archives. This is how the rar container is designed for
and doesn't have the limitation of Zip/7zip Containers.

That's a very bad idea for security.

There is no real security, if you don't use header encryption,
rar5 container with blake2 hash, that is modified by a password.
With the currently created rar archives in TC, you can guess the content
by filenames and crc32 checksum.

If you seriously using archives with TC on daily basis, than you have to
stick with RAR, because Zip/7zip have too limited container format and
features (I don't mean the the strong 7z compression).

Because of this fact and the very limited option in TC to change
compression parameters on the fly, there exists is a lot workarounds
for power users, like command line wrappers, rar.ini, rar profiles,
password manager, live wincmd.ini changer, exe files named "winrar.exe"
with special "version" numbers to let TC think this is Winrar,
alternative rar filenname extension so other tools can change/proof password from command line. etc.

So this "new feature" stops the most of them, because there are a
unwanted password dialog prompted, that can't handled automaticly.

So, If you introduce such a big change in handling archives after 10 years
or more, this should be optional. There are so much ini parameters for
packers, 1 more won't hurt. Btw, in general, for any kind of automatisation
there should be an option to enable or disable, not forced.

Again, this is a absolute showstopper for me, using TC any futher, and I'm
pretty sure, for a lot other people too, because of the many existing workaround/tools found on the internet.

[petermad]

So, If you introduce such a big change in handling archives after 10 years
or more, this should be optional. There are so much ini parameters for
packers, 1 more won't hurt. Btw, in general, for any kind of automatisation
there should be an option to enable or disable, not forced.

I agree.

[ghisler(Author)]

I don't understand why you make such a fuss about such a small change. But it's not hard to add an ini option, so I will add it:
New option wincmd.ini
[Packer]
PackEncrypted=1
Determines when to check "Encrypt" option in pack dialog:
0=never,
1=when target contains encrypted files,
2=always (32/64)

[Biozynotiker]

I don't understand why you make such a fuss about such a small change.

- Because it's not so small as may you think, if you must handle more than 500+ archives a day.
- Because it was forced and make TC nearly unuseable for a lot power users.

But it's not hard to add an ini option, so I will add it

Thanks for that and the fast fixing @beta4, I really appreciate it!