https://bugs.kde.org/show_bug.cgi?id=479567
--- Comment #2 from Ingo Klöcker <kloec...@kde.org> --- Andreas, thanks for identifying the cause of the original report. Some remarks for the additional issues mentioned by Andreas Hartmann in comment #1: > - If you encrypt a tar.gpg file, the timestamps of all encrypted files are > lost. They all have the actual timestamp. An error which has been fixed some > time ago and now is there again. I doubt this ever worked with gpgtar, but in the past we have used tar+gpg instead of gpgtar and tar does preserve timestamps. Unfortunately, gpgtar doesn't. That's tracked by https://dev.gnupg.org/T5054. > - The directory structure is broken through decrypt. A given directory > structure in tar of /1/2 is decrypted to /1/1/2 This might be intentional. gpgtar never extracts to an existing non-empty directory. If that's not what you are seeing then file a ticket at https://dev.gnupg.org/. > - Filenames seam to be interpreted during decryption. Therefore, some > filenames can't be written to disk, because it's data garbage. This looks like https://dev.gnupg.org/T4554. I created an archive with the filenames you listed (with gpgtar --create and copies of a random PDF file), but I could extract it without problems (with gpgtar --extract). Maybe encryption/decryption is required to trigger the problem. -- You are receiving this mail because: You are watching all bug changes.
