Break out OpenPGP keychain management into its own crate #66

New Issue

Open

opened 2025-02-11 05:33:26 +00:00 by ryan · 0 comments

ryan commented

2025-02-11 05:33:26 +00:00

Owner

Most operations in Keyfork Shard can make use of PIN reuse, but when using Keyfork Shard and a separate signing system (for example, icepick workflow --add-signature-to-quorum), there should be some kind of system to properly manage keyrings.

This could probably be accomplished through a PIN manager singleton, or a Sequoia manager singleton. I'm unsure of what option would be best. PIN manager singleton would probably be the easiest to accomplish, but isn't self-containing.

Most operations in Keyfork Shard can make use of PIN reuse, but when using Keyfork Shard and a separate signing system (for example, `icepick workflow --add-signature-to-quorum`), there should be some kind of system to properly manage keyrings. This could probably be accomplished through a PIN manager singleton, or a Sequoia manager singleton. I'm unsure of what option would be best. PIN manager singleton would probably be the easiest to accomplish, but isn't self-containing.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/keyfork#66

No description provided.