Open in browser

[janwillemmulder]

When I click "Open in browser" Chrome states that the security certificate is not secure... (image in Dutch, apologies)

[vinipsmaker]

TLS security model rely on some third party authority to certify/verify identities. Check this for details.

When you run the trsst without the option --clear, it'll use HTTPS (HTTP on top of TLS) with a newly created certificate (I cannot give details about creation of this certificate) and no Certificate Authority have recognized this certificate. Chromium, firefox and all major browsers will give you this warning and you can proceed without problems.

If you plan to run the application remotely, I suggest you to use Firefox and save the exception permanently, then Firefox will remember the application identity (doing the CA's job).

If you see this issue on a remote application, do not trust. But you're on a local environment, then I see no much problem.

Summarizing, if you want to get rid of this message, run the application with the option --clear.

[mmpowers]

Exactly right. Every client app is running it's own hub which generates a self-signed certificate so that you don't have to buy one from a certificate authority in order to secure your connections. Trsst clients don't require signed certs because we rely on TLS mainly to obscure the HTTP headers and traffic patterns, not to guarantee the identity of the relay host. There may be a Man-In-The-Middle, but given that your entries are signed and chained and possibly encrypted, the worst the MITM could do is refuse to relay your entries.

But bottom line: that message is meant to sound scary, but isn't a problem in this case.