Skip to content

Move crystal-relay-key to 1Password, remove hardcoded secret paths #36

@lesaai

Description

@lesaai

Context

~/.ldm/secrets/crystal-relay-key and ~/.openclaw/secrets/crystal-relay-key existed on disk. Parker trashed both. The key needs to live in 1Password and be pulled at runtime like every other secret.

What the key is

The crystal-relay-key is an encryption key for Crystal Relay. Relay is the encrypted tunnel that syncs memory between devices (Mac mini to MacBook Air). The key encrypts chunks before they leave the machine. The cloud Worker (Cloudflare) only sees encrypted blobs. Same key on both machines = they can read each other's data.

What needs to happen

  1. Review crypto.ts ... it has RELAY_KEY_PATH that checks ~/.ldm/secrets/ then falls back to ~/.openclaw/secrets/. Both paths are wrong. The key should come from 1Password via op-secrets, same as every other secret.
  2. Store the relay key in 1Password (wipcomputer.1password.com) so it can be pulled at runtime and shared across machines.
  3. Remove the resolveSecretPath() helper in ldm.ts (or wherever it lives) that reads from ~/.ldm/secrets/. That directory shouldn't exist.
  4. Remove the duplicate op-sa-token from ~/.ldm/secrets/. The only copy should be at ~/.openclaw/secrets/op-sa-token. It's also being backed up to 1Password.

Why

Parker: "I don't like this idea that we made something called Secrets and put in secrets." 1Password is the secrets store. Having a secrets/ directory on disk contradicts the architecture. (transferred from private#47)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions