Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
Hi there,
there were some security issues fixed in 7zip:
https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
https://www.zerodayinitiative.com/advisories/ZDI-23-1164/
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
Hi,
From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
But it seems, it tries to download PAVD2021.EXE.
Thanks
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
Unsolved OpenPGP Support
-
Both 2016 and 17 encrypt to every public key I have, no matter who or how many recipients I choose. If I choose only one recipient, out of five possible recipients, the file will be encrypted to all five instead of just the one selected. Is this a bug or am I doing something wrong?
-
I can confirm this, and there seems to be more work with the encryption of files :'(
- In the key selection dialog, I see other keys, than in my default key manager, so somehow, PowerArchiver uses its own keyring, but doesn’t sync it properly.
- I’m not able to display the trust values of the keys
- The back arrow in the key selection window has no function, the back arrow in the password window cancels the operation and closes the dialog (while a 0 byte file stays behind)
- The password dialog isn’t intuitive at all - it’s the dialog for creating a new password - you need to retype the password, you get a warning on weak passwords and a password policy is displayed. But actually, you need to enter the existing password of your private key
- It seems you can’'t create an encrypted file without signing it
-
It definitely has issues with PGP and keys. I reported a bug well over a year ago about it not displaying the name on the key correctly and so far it has not been fixed.
I believe you always have to sign a file to encrypt it. That is part of the PGP standard.
-
I’ll go ahead and share my other issue with the GnuPG support.
If I have more than one private key, I’m asked to enter a password (for signing) for each private key I have - even though I’ve selected only one signing key and only one is possible.
So here’s the drill:
Let’s say my keyring has ten public keys of others and two personal key-pairs of my own. I want to encrypt to one of my personal keys and one other key - and sign with one of my two private keys. So I choose myself and one other recipient, for a total of two recipients. Obviously I will have chosen only one of my two keys for signing. I will be asked to enter passwords for both of my private keys and the file will be encrypted to twelve recipients! My actual keyring is decades old and contains dozens of keys. Using it with PA is therefore impractical.
As for making signing of files compulsory, all I will say is that most, if not all, GnuPG front-ends allow encryption without signing, including GPA and Kleopatra.
-
@RobertM said in OpenPGP Support:
As for making signing of files compulsory, all I will say is that most, if not all, GnuPG front-ends allow encryption without signing, including GPA and Kleopatra.
I stand corrected. I thought that you needed to sign a file as part of encrypting to certify it but I looked again and you are correct.
Now hopefully PA can fix the issues with PGP
-
will take a close look at the reported issues and log issues in/report back as necessary.
thanks very much all for the details
-
@bigdog said in OpenPGP Support:
I believe you always have to sign a file to encrypt it. That is part of the PGP standard.
No, I can perfectly encrypt files using GnuPG without signing. Even in strict OpenPGP mode.