>mfw If you don’t check “Encrypt file names” in 7-Zip, then only the file contents are encrypted. the central directory headers remain plaintext, and zip2john sometimes interprets that as “not encrypted” when it parses the archive
maybe the script will do the trick7z2john.pl file.zip > hash.txt
7z2john.pl file.zip > hash.txt
>freetards can't design things and come up with something awful>freetards suffering the consequences and frogposting awful threads to ventmust be another day ending in y
>>106435879on the command-line this is the option -mhe=on, so to create an encrypted archive with encrypted archive header use7z a -mhe=on -p archive.7z <files>should have rtfm: https://linux.die.net/man/1/7z
7z a -mhe=on -p archive.7z <files>
>>106436000you use AI, don't lie
great to know. there is no way to crack this file. that's the right way to encrypt files
>>106436000>DO NOT USE the 7-zip format for backup purpose on Linux/Unix because : - 7-zip does not store the owner/group of the file.So how do you achieve the same level of compression on Linux?
>>106438555tar + xz or bzip2. You could probably also use tar + 7z, but I’ve not seen it in the wild. Generally in the Unix world the tar file stores the structure of the archived files, then that is sent through the compression algo, meaning you can use whatever compression algo you want without worrying about whether it stores permissions or whatever.
>>106438555>7-zip does not store the owner/group of the file.why does the owner and group even matterall those unix permissions and other bullshit only mattered on 1970s mainframes where you actually had multiple users on a PC
