Fill in the Spelunk API key on the Security page, as a synced Spelunk key that goes only to its own address

Conversation 0 Commits 1 Files Changed 37

+3907 -64

1 Commits

Author	SHA1	Message	Date
jaap-jan	b08f2c58e3	Fill in the Spelunk API key on the Security page, as a synced Spelunk key that goes only to its own address ci / build and test (pull_request) Failing after 3m42s Details ci / desktop nightly (pull_request) Skipped Details ci / api image (pull_request) Skipped Details ci / android head (pull_request) Successful in 5m24s Details Settings → Security gains a SPELUNK section: an API address and a key, saved as a new keychain item, a Spelunk key (SyncEntityType 14, AadResourceType 17, server table spelunk_key via the AddSpelunkKeyItem migration). It is ciphertext only on the server, lives in the personal vault, syncs like every secret, and holds the key together with the one address it may be sent to. The key box empties once saved; the list shows name, address and how many hosts use each key, never the key. Saving a key for an address that already has one replaces it, and deleting goes through the shared confirmation card with the hosts that would stop connecting. A host's route names a saved key where it named a credential, in the same apiKeyCredentialId field, so no host schema changes and an older build reads such a host as one whose key credential has gone. At connect a saved key is sent only to its own address; a host naming it with another Spelunk address is refused in words. Keys kept as a credential's password still work. The editor offers saved keys first and picks the one saved for an address as it is typed. A link from a Spelunk with a saved key now connects straight away, including the first one: saving the key is the user's say-so that the first-link editor used to ask for. The address and key merge as one pair, so two concurrent edits can never pair one device's key with another's address, and the key never reaches the conflict log.	2026-09-29 10:34:38 +02:00

Author

SHA1

Message

Date

jaap-jan

b08f2c58e3

Fill in the Spelunk API key on the Security page, as a synced Spelunk key that goes only to its own address

ci / build and test (pull_request) Failing after 3m42s

Details

ci / desktop nightly (pull_request) Skipped

Details

ci / api image (pull_request) Skipped

Details

ci / android head (pull_request) Successful in 5m24s

Details

Settings → Security gains a SPELUNK section: an API address and a key, saved as a new keychain item, a Spelunk key (SyncEntityType 14, AadResourceType 17, server table spelunk_key via the AddSpelunkKeyItem migration). It is ciphertext only on the server, lives in the personal vault, syncs like every secret, and holds the key together with the one address it may be sent to. The key box empties once saved; the list shows name, address and how many hosts use each key, never the key. Saving a key for an address that already has one replaces it, and deleting goes through the shared confirmation card with the hosts that would stop connecting.

A host's route names a saved key where it named a credential, in the same apiKeyCredentialId field, so no host schema changes and an older build reads such a host as one whose key credential has gone. At connect a saved key is sent only to its own address; a host naming it with another Spelunk address is refused in words. Keys kept as a credential's password still work. The editor offers saved keys first and picks the one saved for an address as it is typed.

A link from a Spelunk with a saved key now connects straight away, including the first one: saving the key is the user's say-so that the first-link editor used to ask for.

The address and key merge as one pair, so two concurrent edits can never pair one device's key with another's address, and the key never reaches the conflict log.

2026-09-29 10:34:38 +02:00

Fill in the Spelunk API key on the Security page, as a synced Spelunk key that goes only to its own address #21