Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self-signed certificate #789

Open
opk12 opened this issue Mar 4, 2024 · 0 comments
Open

Self-signed certificate #789

opk12 opened this issue Mar 4, 2024 · 0 comments
Labels
bug Something isn't working feature New feature or request security related to security or privacy

Comments

@opk12
Copy link

opk12 commented Mar 4, 2024

My homeserver is in a private network and has a self-signed certificate.

Like Element and the other clients, Syphon should

  1. on the first connection, save the cert
  2. on every connection, check if the cert has changed
    2.1. fail, if the cert has changed

Today it does not log in, because the certificate is not installed on the phone and is not trusted by the root CAs.

In the case of a public domain, self-signed is a red flag. Maybe the app could expect self-signed if a private IP address was typed (as it's impossible to have a CA-signed cert) and then do TOFU.

I could add the cert to the system trust store, but I'd rather do TOFU in-app than have users let strangers put hands on the system settings, possibly outside the trust store.

@dnisbetjones dnisbetjones added bug Something isn't working feature New feature or request security related to security or privacy labels Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working feature New feature or request security related to security or privacy
Projects
None yet
Development

No branches or pull requests

2 participants