• 1 Post
  • 1.76K Comments
Joined 3 years ago
cake
Cake day: July 11th, 2023

help-circle
  • Sure, but at the end of the day even if you don’t update your vaultwarden server or you rely on an insecure storage sync system like dropbox, your actual vault is encrypted with a key that only you know. Even if your server is hacked or the kdbx is leaked, your passwords are safe until someone breaks AES.

    not really the case: https://lemmy.ml/comment/24008121

    Contrast that with hosted services, who could very easily attach their own keys to your encryption key

    how would official Bitwarden be able to accomplish that? apart from this vulnerability, they can’t use their servers to add their own keys.










  • If the drives added to the pool need to be formatted, is there a possibility that it wipes the data on it?

    that’s what I meant, yes, but you said you have 2 16 TB drives right? at least with ZFS, setting up a mirror can be done only starting with a single drive. It’s a godsend.

    first, you take the empty drive, check that it’s actually empty, and if so, create a ZFS pool of a single drive from it, with zpool create. copy all your data over. you can use rsync, it has a bunch of options for preserving most filesystem metadata, and for printing progress.

    when done, check that absolutely everything got transferred, and add the other 16 TB drive too to the pool with zpool attach. doing this will convert the pool with only a disk vdev, into a pool with a mirror vdev of 2 disks.

    further recommended reading: https://openzfs.github.io/openzfs-docs/man/master/8/zpool.8.html

    you may want to enable compression from the beginning. if you do it later, existing data won’t be compressed. media files mostly don’t benefit from this. compression is enabled on the dataset level, with the zfs command, if you set it to lz4 (recommended alg) for the root dataset, everything will be compressed that way.