On Sun, Sep 12, 2021 at 4:41 AM Amos T <[email protected]> wrote: > So in my store I see a few issues: > > 1) it looks to me there is no versioning in s3ql either. This means that > feels very uncomfortable to me seen the new range of virii >
Perhaps I misunderstand your meaning for "versioning". s3ql is a file system, not a backup tool. If you're after a backup (providing earlier versions of files) stored in your s3ql file system, then use a backup tool that writes into the s3ql file system. Have you read the following? https://www.rath.org/s3ql-docs/contrib.html#s3ql-backup-sh 3) there is no parity on the s3ql_data_* files , I like to see some error > detection and correction there in the form of s3ql_data_NNNNN.par2 (for > each data block) > and additional s3qlcmd to verify and if needed repair on that level in > a worse case scenario... > >From the s3ql Features list: "Encryption. After compression (but before upload), all data can be AES encrypted with a 256 bit key. An additional SHA256 HMAC checksum is used to protect the data against manipulation." Manipulation or corruption, a block will fail to decrypt if something goes wrong. -- -:-:- David K. Gasaway -:-:- Email: [email protected] -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/CAGsJ5AXeKQaTmWO0ZH%3DcJaBgYodwZ1acn1eFdE2uT%3DCD0nuDWQ%40mail.gmail.com.
