d00bd369b7
s3d binds one Sia account per process, so the server runs one s3d per person (pithos-hosted), started on demand and flushed and stopped when idle. Only the connected s3d data folder moves between PC and server; the Sia recovery phrase never leaves the PC and nothing is re-uploaded to Sia. Because the server holds the connection key, local Pithos encrypts names and contents before they leave the machine, with keys from the Theseus vault (or a local key file elsewhere). What s3d cannot do on its own, the gateway now enforces: public folders, expiring share links and S3 keys for other people limited to one folder with read, add-only or edit rights. Files those reach are stored readable, since visitors have no key, and go back to encrypted when the rule is removed. Sign-up needs a BNS name signature, a deposit or an invite, with a per-IP limit.
22 lines
522 B
Desktop File
22 lines
522 B
Desktop File
[Unit]
|
|
Description=Pithos on Silent Mode (hosted s3d gateway)
|
|
After=network-online.target
|
|
Wants=network-online.target
|
|
|
|
[Service]
|
|
User=pithos
|
|
Group=pithos
|
|
WorkingDirectory=/opt/pithos
|
|
ExecStart=/usr/bin/node /opt/pithos/hosted/main.js --config /etc/pithos-hosted.json
|
|
Restart=on-failure
|
|
RestartSec=5
|
|
# Stopping flushes every s3d's leftovers to Sia first.
|
|
TimeoutStopSec=300
|
|
KillMode=mixed
|
|
NoNewPrivileges=true
|
|
ProtectSystem=strict
|
|
ReadWritePaths=/var/lib/pithos-hosted
|
|
PrivateTmp=true
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|