You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am using your tool and it suits my needs perfectly. My use case is this: once a week a cron-job on my VPS triggers this tool to pack all the containers into tars, and then my backup-storage fetches them with rsync. nice and safe. Now I wanted to change the routine, so that the tars are first encrypted via gpgtar and my public-key, and then transmitted and stored encrypted.
Now my problem has come up. Some tarballed dockers have filenames more than 100characters long. gpgtar won't accept filenames that long due to compatibility issues: https://dev.gnupg.org/T2687 (wontfix).
Does this tool have some way of influencing the filenames of the created tar-files? Or alternatively, can this tool directly encrypt the generated tarballs?
thank you very much
The text was updated successfully, but these errors were encountered:
Hi,
I am using your tool and it suits my needs perfectly. My use case is this: once a week a cron-job on my VPS triggers this tool to pack all the containers into tars, and then my backup-storage fetches them with rsync. nice and safe. Now I wanted to change the routine, so that the tars are first encrypted via gpgtar and my public-key, and then transmitted and stored encrypted.
Now my problem has come up. Some tarballed dockers have filenames more than 100characters long. gpgtar won't accept filenames that long due to compatibility issues: https://dev.gnupg.org/T2687 (wontfix).
Does this tool have some way of influencing the filenames of the created tar-files? Or alternatively, can this tool directly encrypt the generated tarballs?
thank you very much
The text was updated successfully, but these errors were encountered: