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
Currently TKLBAM uses a hardcoded duplicity option, --s3-unencrypted-connection. In this day and age, we should default to TLS connections where possible. It's not explicitly a problem in this case as the data is already encrypted and AWS supports unencrypted connections.
However, IMO it should be configurable via a config file.
The text was updated successfully, but these errors were encountered:
Currently TKLBAM uses a hardcoded duplicity option,
--s3-unencrypted-connection
. In this day and age, we should default to TLS connections where possible. It's not explicitly a problem in this case as the data is already encrypted and AWS supports unencrypted connections.However, IMO it should be configurable via a config file.
The text was updated successfully, but these errors were encountered: