Then I found this website, with the same instructions except their command line starts zip -er instead of zip e.
Create Passcode For Password Protection AcrossThese encrypted zip files will maintain password protection across platforms, meaning you can send a protected zip file to a Windows user and they will still need to enter the password in order to view the contents.![]() Create Passcode For Archive From TheYou can also decompress the zip archive from the command line with.
Create Passcode For Full Path ToNot with the full path to the file, nor with cd to its directory. If there are spaces in the path surround the entire file name with double-quotes () or put a backslash before each space as in file to protect.txt for file to protect.txt. Terminal will beep at you if it cant find a file matching the name. As a matter of fact, if you type zip -e xmisc.zip filetopr (minus the quotes and then type the Tab key if the file exists Terminal should fill in the rest of the name for you assuming only one match or it will beep if more than one file matches. And I can successfully unzip using Terminal and entering my password. However I cannot simply double click the ZIP file for it to unzip. This leaves me to believe it is a Permissions problem, as suggested above. The permissions for my Desktop are read only for everyone other than the owner (me). How and where should I store the PDF and subsequent ZIP to allow full permissions. I dont want to get into messing around with Desktop permissions, its a slippery slope to never ending problems in my experience. ![]() I have used the terminal command zip -er archive folder as advised above under OS X Mavericks. To extract the ZIP-file in Mavericks I had to enter the password as expected. But the I moved the ZIP-file to Dropbox and downloaded it with Windows Vista. ![]() Trying to open one of the files in the content caused a window to open asking for the password (on file-level not on archive-level). After I entered the password as used for creating the archive under Mavericks resulted in an error message like the file cannot be opened, it may be damaged. Using Microsoft OneDrive instead of Dropbox resulted in the same behavior. I am too lazy to test now the other way round, if I would create a password protected ZIP-archive in Windows and send this one to Mavericks but I would expect this way to work. My conclusion: it seems like the Apple way does not keep the conventions. Be sure the file did not get corrupted in the transfer process, and be sure to use a compatible zip archive opener utility (on Windows you can try something like WinZIP if you have troubles).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |