We got feedback from 2 customers that when decrypting a file or archive to a network drive they get the message that it could not be written to the folder, they should choose another one.
Encryption works fine, Decryption on cli to that folder works, too.
Might be related to the fix for https://dev.gnupg.org/T6499
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA655abf9a75e5 Create temporary file to check if output folder is writable | |||
| rKLEOPATRA62b6f5d480eb Do not use NTFS permissions check to check if output folder is writable | |||
Another hint: When they checked "write temporary files in the folder of the encrypted file" they got a message window from gpgex "Error returned by the GnuPG user interface: Input/output error".
Filesystem is NTFS, they use only NTFS permissions, share is SMB drive on a Synology NAS and encrypted by the NAS.
In a first commit, I have switched back to the simple check done by QFileInfo::isWritable() (see https://doc.qt.io/qt-5/qfileinfo.html#isWritable).
In a second commit, a temporary file is created in the output folder to check if it is writable.
I recommend to backport only the first commit to VSD 3.2 (which restores the behavior of the previous VSD version).