{ "id": "e80455218f370d54196be5146baf3552cada0bfc3843bd613e5b9650c288f996", "pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58", "created_at": 1730585590, "kind": 1621, "tags": [ [ "subject", "[Feature Request] External Credential Managers (signers)" ], [ "alt", "git repository issue: [Feature Request] External Credential Managers (signers)" ], [ "r", "26689f97810fc656c7134c76e2a37d33b2e40ce7" ], [ "a", "30617:a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d:ngit", "wss://relay.damus.io", "root" ], [ "p", "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d" ] ], "content": "I'd like to start using git via nostr, but I'm extremely strict about how I interact with my keys. My secret key is locked up in a vault and not exportable on purpose. My signer does not currently work with nip46 and I have my issues with nip46 as well. That said I would like to see if there is interest for the ability to create an IPC api for external credential managers. Similar to git cli, ssh and so on. \n\nSuggestions:\n- Possibly connecting to a locally running process via pipes or sockets\n- Starting a child process of the credential manager to pass cryptographic event's to to sign/verify. \n\nI think we could safely assume passing JSON encoded messages between processes would make the most sense. \n\nIn the future this would easily allow hardware signer support (especially if we created a simple protocol) ", "sig": "d72e9f0e32a44298d3c0f03b1429bac1fb602eec17b0bb65f47a5b723a86e9fafa0c4596affaffc3ee8be7a1ed6961cd068272a5f0fbfe3a86248a11f45a7a0a" }