In Theseus, Pithos now opens only with the vault unlocked: it asks Theseus for the unlock (api.vault.requestUnlock), and Theseus shows its own PIN prompt, falling back to the master password after three wrong tries. Pithos never sees either. When the vault locks (Settings > Lock now) Pithos locks within a few seconds; the add-on watches from the main process because a hidden panel's timers run about once a minute. The guide's phrase step gains "Use my Theseus vault" (the default when a vault exists): the add-on derives the 12-word phrase from the vault (purpose path pithos/sia-recovery/v1, first 16 bytes as BIP-39 entropy) and hands it straight to s3d, so there is nothing to write down and the vault backup restores storage access. The path is now fixed; changing it would cut users off from their data. Needs the vault-derive capability. On a Theseus without requestUnlock it runs ungated, as before.
28 lines
640 B
JSON
28 lines
640 B
JSON
{
|
|
"name": "pithos",
|
|
"version": "0.3.0",
|
|
"description": "A control panel for s3d, the Sia S3 gateway: daemon, users and keys, buckets, upload pipeline.",
|
|
"license": "MPL-2.0",
|
|
"type": "module",
|
|
"main": "core/server.js",
|
|
"bin": {
|
|
"pithos-web": "bin/pithos-web.js"
|
|
},
|
|
"scripts": {
|
|
"web": "node bin/pithos-web.js",
|
|
"desktop": "electron desktop/main.cjs",
|
|
"test": "node --test test/*.test.js"
|
|
},
|
|
"engines": {
|
|
"node": ">=20"
|
|
},
|
|
"dependencies": {
|
|
"yaml": "^2.9.1"
|
|
},
|
|
"optionalDependencies": {
|
|
"@lydell/node-pty": "1.2.0-beta.15"
|
|
},
|
|
"devDependencies": {
|
|
"electron": "^44.5.1"
|
|
}
|
|
}
|