We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a function to determine whether the metadata is encrypted? Now bit7z can only use exceptions to determine whether the metadata is encrypted.
No response
The text was updated successfully, but these errors were encountered:
Add functions to check whether an archive is encrypted/header-encrypted
d194234
Close issue #164
Hi!
Thanks for the suggestion!
I've just pushed a commit (d194234) that adds two static functions to the BitArchiveReader class:
BitArchiveReader
template< typename T > auto BitArchiveReader::isHeaderEncrypted( const Bit7zLibrary& lib, T&& in_archive, const BitInFormat& format ) -> bool; template< typename T > auto BitArchiveReader::isEncrypted( const Bit7zLibrary& lib, T&& in_archive, const BitInFormat& format ) -> bool;
They're template functions so that they can accept either a file path (string), a buffer, or a standard stream of the archive to be checked.
BitArchiveReader::isHeaderEncrypted checks whether the archive is fully encrypted (header included), and hence it needs a password to be opened.
BitArchiveReader::isHeaderEncrypted
BitArchiveReader::isEncrypted checks whether the archive contains only encrypted files, but can be opened without a password (plain headers).
BitArchiveReader::isEncrypted
These functions will be included in the stable version of bit7z v4.
Sorry, something went wrong.
Implemented in v4.0.0.
rikyoz
No branches or pull requests
Feature description
Adding a function to determine whether the metadata is encrypted? Now bit7z can only use exceptions to determine whether the metadata is encrypted.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: