Alyssa Rosenzweig
b49a7b490f
Switch to set
|
5 tahun lalu | |
|---|---|---|
| accounts | 5 tahun lalu | |
| .editorconfig | 6 tahun lalu | |
| .gitignore | 5 tahun lalu | |
| LICENSE | 5 tahun lalu | |
| Makefile | 5 tahun lalu | |
| README.md | 5 tahun lalu | |
| cert.sh | 5 tahun lalu | |
| core.c | 5 tahun lalu | |
| core.h | 5 tahun lalu | |
| event-loop.c | 6 tahun lalu | |
| event-loop.h | 6 tahun lalu | |
| jailed.sh | 5 tahun lalu | |
| json_compat.h | 6 tahun lalu | |
| proxy.c | 5 tahun lalu | |
| push.c | 5 tahun lalu | |
| push.h | 5 tahun lalu | |
| sapphire-accounts.json | 5 tahun lalu | |
| secure-compare-64.h | 5 tahun lalu | |
| websocket.c | 5 tahun lalu | |
| websocket.h | 5 tahun lalu |
README.md
Backend
sapphire-backend communicates only over local filesystem-resident sockets, to simplify jailing. To reach the outside world -- in particular, to benefit from websockets -- it must be paired with sapphire-proxy, which implements proxying, authentication, and SSL.
To set this up, use:
$ ./sapphire-backend & ./sapphire-proxy
And if you need to restart, it's probably safest to quit both.
This process might be further streamlined in the future.
Proxy
Historically, on a local single-user Sapphire instance, the architecture was simple:
Browser <--> Backend
However, this does not work for multi-user, public-facing instances. In these cases, to minimise attack surface, this proxy is publicly facing while the backends only listen to localhost and are sandboxed:
Browser <--> Proxy (<--> Backends)
This package proxies WebSockets and implements authentication. It therefore depends on glib/json-glib/libsoup, but it MUST NOT depend on libpurple due to security isolation concerns.