3 ms·
Unfortunately restic was a no go for me due to not being compatible with B2 keys that only have the permissions readFiles,writeFiles,listBuckets,listFiles (no d
by fletchowns 6y ago
Unfortunately restic was a no go for me due to not being compatible with B2 keys that only have the permissions readFiles,writeFiles,listBuckets,listFiles (no deleteFiles). I don't want the attacker to be able to delete any backups if the manage to get to the B2 keys.
I believe this is the ticket that would add support for this to restic: https://github.com/restic/caddy/issues/2 https://github.com/restic/caddy/issues/2
- pricechild 6y agoYou can work around this by sticking rclone in the middle which does support soft delete: https://pricey.uk/blog/restic-backups-without-delete/ https://pricey.uk/blog/restic-backups-without-delete/ In short, give rclone your keys, (small ~/.rclone config file) tell restic to use an rclone backend and add an extra argument when running restic. (See the blog link above, all explained) There's an open issue for this which doesn't seem to have moved: https://github.com/restic/restic/issues/2134 https://github.com/restic/restic/issues/2134 - it does have a couple of PRs linked on there which implement proper soft-delete.
- fletchowns 6y agoNice blog post! That's exactly what I needed earlier last year when I was looking at this stuff :) Looks pretty straightforward. I am surprised it is not more of a priority to get merged though, it is so essential.