-
Hi,
I’d like to propose an improvement for password protected archives.
Actual behavior is:
If I open an archive, which is password protected and make a typo in the password dialog, I’ll get the message, that the password was wrong and I end up with an empty window. I need to reopen the archive to be able to enter the password again.Improved behavior:
Tell me, that the password was wrong and give me the chance to enter the correct password to decrypt the archive. -
Hello!
I know I have been asking for this feature some time ago, but as nothing has changed let me ask again:
The ZIPX-format offers an algorithm, that compresses JPEG-files by about 20-30%. Please add compression (packing) support for this in ZIPX-archives to Powerarchiver. Extraction of JPEGs packed into ZIPX by this algorithm is already supported by Powerarchiver for a long time, so it should not be difficult? Or is it a licensing problem?
Thanks! -
Hi,
I’d like to suggest, that the correct archive type is (always) selected, when adding files by drag & drop to an archive.
This is already happening if the archive has the correct extension. For example, if I’m adding files to test.zip, zip will be selected. If I’m adding files to test.7z, 7z will be selected as format in “Add dialog”.
But this won’t be working, if the archive has not the “right” extension.
So XPI files (Firefox addons) for example are ZIP files. PowerArchiver opens them without any problems, but if I try to add file by drag & drop, PowerArchiver won’t auto select “ZIP”, but use the last selected archive format, while PowerArchiver already knows, that I’m trying to add files to a ZIP. -
I love this, only there is one problem. The UAC elevation feature does not extend to Mount Image option in the add-on software PA provided. It is most annoying whenever I am on highest UAC settings and I mount an ISO, every time I open and create a virtual drive UAC appears. I also do not want to completely disable UAC.
Is adding UAC elevation for mount image feature possible?
-
The now defunct Bulkzip had Nanozip (nz) as an option this would be great to have for compatibility with my .nz files, so I don’t have to install Bulkzip separately.
-
Hi.
I noticed that when I want to run the Virtual Drive for the first time inside the PowerArchiver Burner it prompts to download it form the internet.
I was wondering, would it be OK to include this utility straight into the offline installer to be able to set it up locally?
Thank you!
-
How about recognising a few more (or all) of the file formats that are basically renamed zip files and treating them is if they are zip files.
For instance Android .apk files are just renamed .zip files.
Libreoffice/Openoffice ODF documents are all, as far as I am aware, just renamed .zip files. (.odt, .ott, .ods, .ots, .odp, .otp, .odb, .odf etc.) -
-
-
Would it be possible at all in some future version perhaps, to have a “find file” function?
Reason I ask is that I was looking for a certain file I knew existed in an archive, but I had to unzip it then use another tool to find the file. It would have saved that extra step if that function existed in PA itself. -
Hi.
Is there a way to enable the user to encrypt the files inside a ZIPX archive that has already been created?
This could save time for large archives that the user may need to encrypt at a later stage or that he/she has forgotten to enable encryption before creating the archive,
Thank you!
-
Hi.
I would like to see a new feature implemented: a ‘Fast Extract’ Mode.
Currently PowerArchiver extracts files to a temporary directory and then moves them to the target directory chosen by the user. At least via drag and drop.
This can be both time consuming and needs free space on the system drive for large files.
Is there a way to directly extract files to the target directory with PowerArchiver?
And if not, can a feature like this be considered for future updates?Thanks very much!
-
Hello.
I believe it would be useful to implement Serpent-256 encryption for PAE/PAE2 formats, even though PowerArchiver offers strong encryption ciphers already.
(deleted part advertising other software - admin)
Do you think this will be a useful addition?
Thank you for the consideration!
-
Hello!
I think it would be a great option to make the portable version of PowerArchiver compatible with PortableApps (i.e. adding the necessary files and folders to integrate it smoothly into their structure).
I own various other commercial programmes which -when installed in portable mode- offer to make the becessary changes without needing an extra installer or the official PortableApps repos.
Thanks for opinions or perhaps even a realization of this.
A.Borque -
Presently, PowerArchiver 2019 (any build) cannot rename PBS filenames by single clicking on such entry or right-click menu has no “Rename” feature!
Hmm, even pressing F2 on selected entry does nothing :(
-
Please add support for ownCloud / Nextcloud, thanks.
-
-
SOLVED Serpent-256 Encryption for PAE/PAE2
-
Hello.
I believe it would be useful to implement Serpent-256 encryption for PAE/PAE2 formats, even though PowerArchiver offers strong encryption ciphers already.
(deleted part advertising other software - admin)
Do you think this will be a useful addition?
Thank you for the consideration!
-
btw, by far the most secure is to use PA format with secure option:
Secure AES 256-bits - creates PA archives with AES 256-bit encryption. For added security, we use the BWTS algorithm to scramble the data before AES, so attackers can not use LZ compression redundancy and other plaintext attacks to quickly check if given password is valid. This makes .pa format considerably more secure than ZIP AES. For the AES encryption module, we use FIPS 140-2 validated modules from Windows so you can rest assured that AES implementation has been tested and validated (FIPS 140-2 encryption module is always used)"
-
Are you hoping for the ability to open encrypted archives from PEA?
-
Or is this just SPAM advertising PEA?
-
My thoughts is the latter. Will wait for @spwolf to judge.
-
btw, by far the most secure is to use PA format with secure option:
Secure AES 256-bits - creates PA archives with AES 256-bit encryption. For added security, we use the BWTS algorithm to scramble the data before AES, so attackers can not use LZ compression redundancy and other plaintext attacks to quickly check if given password is valid. This makes .pa format considerably more secure than ZIP AES. For the AES encryption module, we use FIPS 140-2 validated modules from Windows so you can rest assured that AES implementation has been tested and validated (FIPS 140-2 encryption module is always used)"
-
Hi.
I did not mean the link to be for advertising. The link was based on an open source software documentation/comparison that would support my request.
Of course, everything was just for suggestion purposes, to see if you think it’s worth implementing this feature.
My wish was centered on the encryption cipher itself. :)
Thank you!
-
@2Flo So, I ask again, are you hoping for the ability to open encrypted archives from PEA?
-
Hi.
Essentially my wish would be to have the Serpent-256 encryption cipher as an option to encrypt any data.
The archive format doesn’t matter for me, I wish I had the option to create and open Serpent-256 encrypted [any supported archive / file type] from PowerArchiver.
Thank you! :)
-
@2Flo Because you believe it’s more secure than AES256 ?
I guess by some particular means of assessing the security of a cypher it may seem more secure.
But it’s also less efficient to implement than AES256.
PowerArchiver has chosen, IMHO quite reasonably, to go with the industry standard widely accepted and respected, more efficient, AES algorithm.:face_with_stuck-out_tongue: -
Hi.
Indeed, while Serpent uses a more conservative approach than AES with regards to security margin, it is slower in implementation and not that much public cryptoanalysis has been done on it compared to AES.
I was thinking about it for completion sake.
The reference code is public domain software and the optimized code is under GPL license.Since PowerArchiver already supports AES, 3DES, RC2, RC4, Blowfish, and Twofish
and Serpent was also an AES finalist, I wondered if it could join the list of supported encryption ciphers.Of course that Rijndael (AES) is still very secure, not broken, fast in implementation and universally supported.
It will remain to the developers’ decision wether Serpent is worth implementing. Nevertheless, PowerArchiver supports strong encryption ciphers and the addition of another is purely optional.
Thank you!
-
@2Flo said in Serpent-256 Encryption for PAE/PAE2:
Hi.
Indeed, while Serpent uses a more conservative approach than AES with regards to security margin, it is slower in implementation and not that much public cryptoanalysis has been done on it compared to AES.
I was thinking about it for completion sake.
The reference code is public domain software and the optimized code is under GPL license.Since PowerArchiver already supports AES, 3DES, RC2, RC4, Blowfish, and Twofish
and Serpent was also an AES finalist, I wondered if it could join the list of supported encryption ciphers.Of course that Rijndael (AES) is still very secure, not broken, fast in implementation and universally supported.
It will remain to the developers’ decision wether Serpent is worth implementing. Nevertheless, PowerArchiver supports strong encryption ciphers and the addition of another is purely optional.
Thank you!
PAE format is there for legacy purposes these days… real meat is in Secure 256 AES implementation we do in PA format, with some extra work that makes brute force attacks harder to use.
-
@spwolf said in Serpent-256 Encryption for PAE/PAE2:
@2Flo said in Serpent-256 Encryption for PAE/PAE2:
Hi.
Indeed, while Serpent uses a more conservative approach than AES with regards to security margin, it is slower in implementation and not that much public cryptoanalysis has been done on it compared to AES.
I was thinking about it for completion sake.
The reference code is public domain software and the optimized code is under GPL license.Since PowerArchiver already supports AES, 3DES, RC2, RC4, Blowfish, and Twofish
and Serpent was also an AES finalist, I wondered if it could join the list of supported encryption ciphers.Of course that Rijndael (AES) is still very secure, not broken, fast in implementation and universally supported.
It will remain to the developers’ decision wether Serpent is worth implementing. Nevertheless, PowerArchiver supports strong encryption ciphers and the addition of another is purely optional.
Thank you!
PAE format is there for legacy purposes these days… real meat is in Secure 256 AES implementation we do in PA format, with some extra work that makes brute force attacks harder to use.
Does this apply to the previously mentioned BWTS algorithm? Or does this apply to increased number of rounds / cipher operation mode / key derivation algorithm / something else?
-
@2Flo said in Serpent-256 Encryption for PAE/PAE2:
@spwolf said in Serpent-256 Encryption for PAE/PAE2:
@2Flo said in Serpent-256 Encryption for PAE/PAE2:
Hi.
Indeed, while Serpent uses a more conservative approach than AES with regards to security margin, it is slower in implementation and not that much public cryptoanalysis has been done on it compared to AES.
I was thinking about it for completion sake.
The reference code is public domain software and the optimized code is under GPL license.Since PowerArchiver already supports AES, 3DES, RC2, RC4, Blowfish, and Twofish
and Serpent was also an AES finalist, I wondered if it could join the list of supported encryption ciphers.Of course that Rijndael (AES) is still very secure, not broken, fast in implementation and universally supported.
It will remain to the developers’ decision wether Serpent is worth implementing. Nevertheless, PowerArchiver supports strong encryption ciphers and the addition of another is purely optional.
Thank you!
PAE format is there for legacy purposes these days… real meat is in Secure 256 AES implementation we do in PA format, with some extra work that makes brute force attacks harder to use.
Does this apply to the previously mentioned BWTS algorithm? Or does this apply to increased number of rounds / cipher operation mode / key derivation algorithm / something else?
mentioned in the wiki and my response above:
For added security, we use the BWTS algorithm to scramble the data before AES, so attackers can not use LZ compression redundancy and other plaintext attacks to quickly check if given password is valid.
it is done after compression and before AES.
-
Thank you for the insight on this! :)