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.
19 lines
456 B
JSON
19 lines
456 B
JSON
{
|
|
"listen": "127.0.0.1:8720",
|
|
"publicUrl": "https://s3.silentmode.st",
|
|
"root": "/var/lib/pithos-hosted",
|
|
"s3dBinary": "/opt/pithos/bin/s3d",
|
|
"portBase": 21000,
|
|
"maxRunning": 30,
|
|
"idleMinutes": 30,
|
|
"bufferLimitBytes": 2147483648,
|
|
"maxDataBytes": 4294967296,
|
|
"downloadCapBytes": 53687091200,
|
|
"trustProxy": true,
|
|
"gate": {
|
|
"bns": { "api": "https://navigate.st" },
|
|
"deposit": null,
|
|
"invites": [],
|
|
"perIpPerDay": 3
|
|
}
|
|
}
|