Comment on Ovumcy (self-hosted period tracker), 9 months later: what I did with your feedback [AIP]
terraincognita@lemmy.world 11 hours agoThese are fair, and the misconfigured server one is the strongest. Client-side encryption would limit the damage there, I can’t argue with that.
The group case is outside what I built this for. It’s meant for a household. If you run it for other people, you become their hosting provider, and the docs say that plainly: the app keeps your records from other accounts and from the network, not from whoever administers the machine.
The VPS point is true, but it applies to everything on that box, not just this app. If you don’t trust the provider with it, the answer is hardware at home.
I won’t promise it, but optional encryption for the web version is on my list to look into now.
On design mistakes: agreed, tests and fuzzing don’t catch a wrong decision. But the SSH example cuts both ways. That code was written and reviewed by very experienced people and it still got through. Nobody is immune, so what matters is whether mistakes get found and fixed in the open. That has already happened here: tonghuaroot reported a hole in the webhook address filter, it was fixed and published as an advisory (GHSA-hg2x-v5cc-m384).