SelfPrivacy
/
wiki.selfprivacy.org
mirror of https://git.selfprivacy.org/SelfPrivacy/wiki.selfprivacy.org.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add backlog to problems.md

This commit is contained in:
Inex Code 2022-02-07 11:25:45 +03:00
parent 8ad175e50c
commit 9474ebbd99
1 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
src/problems.md
View File

@ -1,6 +1,4 @@
# Reproted problems
## No check for invalid DNSSEC setup
If DNSSEC is set up incorrectly, app won't tell user why server can't be set up.
## NixOS fails to upgrade
We have to deploy our own channel with verified builds.
@ -8,9 +6,6 @@ We have to deploy our own channel with verified builds.
## Master user password
Can't use anything but [a-zA-Z0-9]. Problem is in the way we pass variables to nixos-infect script from the app side. String escaping is needed, but it turned out to be not trivial. Use base64 in transit instead? Would have to keep compatability with the old app versions.
## Email can only use [a-z]
Some users wanted emails in format name.surname@domain.tld, but couldn't. As we create unix users, we have to use `r"^[a-z_][a-z0-9_]+$"`. User documentation needs explanations on this?
## Ability to change user passwords
Has to be implemented on both server and app side.
@ -25,21 +20,11 @@ Leads to files corruption?
### User is not notified that they may have to add a credit card to b2
Free limits are pretty small and restoration may easily spend them all, and after that, everything is broken.
## Jitsi
Not working. when fix?
## DKIM
Is not deployed to Cloudflare. Inex working on it right now.
## Problems with international domains
I can't determine the scope of the problems it causes, without having one. But it surely creates a lot of problems on many stages, starting at server creation.
Should we buy an international domain?
## RSA keys generated in app not working
No idea why.
## VPN
Still looking for another protocol.
Will get rid of key generation inside an app.
## Volumes are not used properly
We need a controller which will detect them, format them, expand them and also move apps between them. Probably app should use Hetzner API to expand volume automatically.
@ -50,6 +35,24 @@ Which leads to big problems for the server. API has to control available space,
## Server control is lost when losing app's storage
Solution implemented on API side as recovery tokens in [[changelog#authorization_tokens branch|1.2.0]]. We need to implement this on app side.
# Backlog
## No check for invalid DNSSEC setup
If DNSSEC is set up incorrectly, app won't tell user why server can't be set up.
## Email can only use [a-z]
Some users wanted emails in format name.surname@domain.tld, but couldn't. As we create unix users, we have to use `r"^[a-z_][a-z0-9_]+$"`. User documentation needs explanations on this?
## Jitsi
Not working. when fix?
## Problems with international domains
I can't determine the scope of the problems it causes, without having one. But it surely creates a lot of problems on many stages, starting at server creation.
Should we buy an international domain?
## VPN
Still looking for another protocol.
## HTTP headers on nextcloud are not optimal
X-Content-Type-Options is not set to "nosniff" and X-Frame-Options not set to "SAMEORIGIN".