Comment on Journiv - Self Hosted Journal v0.1.0-beta.11 : Day One Import, Location and Weather, Tag Management and much more are here.

Rogue1633@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

• rockstar1215@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Hello, Encryption at rest is in on roadmap. End to end encryption is very time intensive to build correctly and would be an overkill for a large percentage of users who are self hosting Journiv so as of now there are no plans for e2e.

  source

  • Rogue1633@discuss.tchncs.de ⁨6⁩ ⁨days⁩ ago

    ok thanks for the reply. I understand that this would take very much work but I wouldn’t be comfortable hosting something with potentially very sensitive data on a remote server where the admins could see the files. Unfortunately hosting on my Raspberry Pi at home isn’t possible because of this error when starting the docker containers (which seems to be a Raspberry issue).

    What is the difference between your encryption at rest and disk/file system encryption? Would the use case be that someone stealing the server couldn’t access the files?

    source

    • rockstar1215@lemmy.world ⁨6⁩ ⁨days⁩ ago

      That makes sense. As of now I have not considered the VPS approach you mentioned but only thought of self hosting but I can see how in VPS world it is not safe. Encryption at rest can be obtained by various means

      • Have the disk encrypted like you said.
      • Have the db encrypt by a admin provided secret but in this case all users of instance share that secret and admin can technically decrypt other user data.
      • Have the app do encryption based on user provided password. This gives per user secret and encryption. So encryption at rest will be something among this preferably (3) one.

      source