Hey everyone! :)

I am currently looking to replace Obsidian with a self-hostable alternative (that preferably also uses Markdown - but it’s not a must) but instead of storing the files directly on disk has a way to have all the files within in an encrypted vault / binary format.

Reason being I have very very sensitive data that needs to be stored (employee & medically related).

I read that Logseq used to support this feature but it has since been deprecated, some light googling didn’t surface any results other than that so I would be delighted if anyone had any suggestions!

Thanks so much in advance for any and all help! :)

edit: Forgot to mention that it needs to support Linux as well as Android

22 points

Joplin can encrypt and it is selfhostable and uses Markdown

Benefit: apps for every platform

permalink
report
reply
11 points

After some more research it seems that Joplin only E2E encrypts notes at transport and not at rest[1]? e.g. it only stores plain text files on the harddrive just like Obsidian does? This sadly makes it not viable for my use case :/

[1] https://discourse.joplinapp.org/t/requesting-encryption-of-local-joplin-data-at-rest-encryption/15145

permalink
report
parent
reply
7 points

E2e in transport is https with extra steps 😅

permalink
report
parent
reply
15 points

No it is fully encrypted, even on the server. This topic was years old. You can read a good explanation here

permalink
report
parent
reply
0 points

They do encryption at rest too. Really good notes app and it’s cross platform too. Only missing a “web” client for when you want to access your notes on a computer without Joplin installed (but that defeats the purpose of the E2EE IMO)

permalink
report
parent
reply
11 points

If you are dealing with compliance seek help from a professional

permalink
report
reply
1 point
*

This needs to be reiterated. If you need to comply with ANY laws at all do not perform this service yourself. Consult professionals and allow them to assume that risk.

If all you are doing is trying to encrypt notes you are taking then maybe that’s a different story. Please just make sure you are not at a legal risk.

permalink
report
parent
reply
8 points
*

if you’re encrypting at rest you also have to consider where there encryption key is being stored.

if you’re storing the encryption key plaintext on the same drive as the data, there’s not much of a point in encrypting.

a TPM/HSM could solve the issue, depending on how far down the rabbit hole you need to go.

EDIT: You could also encrypt the disk of the VM/Server hosting the app. similar situation.

permalink
report
reply
2 points
*

In my mind at least this would be solved by the “vault” needing to be decrypted with a password every time notes are accessed/saved with the password acting as the key? I’m not terribly well educated on encryption though.

permalink
report
parent
reply
3 points

The problem is how many random characters can you remember in your head?

A good encryption key would be around 32 characters to form a 256 bit encryption key.

You can do a fun game of encrypt the encryption key with a password but that’s just another vulnerability in the chain.

I recommend getting a PGP key stored on a yubikey and then encrypt all your notes with it since it’s all in markdown, I store my notes on Google drive and keep them decrypted in memory so that I can still use Obsidian.

permalink
report
parent
reply
7 points

Or just use a password manager like keepass where the problem of storing passwords has been solved already…

permalink
report
parent
reply
2 points

if you want to type the key yourself each time this could work. I’m not aware of an app that does this but it wouldn’t be too hard I don’t think.

permalink
report
parent
reply
7 points

You can selfhost Standard Notes. The notes are encrypted client side before they reach the server.

permalink
report
reply
6 points

joplin

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.6K

    Posts

  • 77K

    Comments