MarketTakers/arbiter
5
0
Fork 0
Code Issues 27 Pull Requests 4 Packages Projects Releases Wiki Activity

Implement encryption scheme versioning and auto-migration #15

New Issue
Closed
opened 2026-02-14 11:34:32 +00:00 by Skipper · 1 comment
Skipper commented 2026-02-14 11:34:32 +00:00
Owner
Copy Link

Implement versioned encryption and automatic re-encryption on unseal, as described in ARCHITECTURE.md section 4.2.

The schema_version column exists on aead_encrypted but no migration logic is implemented.

Requirements:

  • Define encryption scheme versions (starting with v1: ChaCha20-Poly1305)
  • On unseal, scan aead_encrypted for entries with schema_version < current
  • Re-encrypt outdated entries with the current scheme
  • Ensure re-encryption is atomic (no partial state on failure)
  • Support adding new encryption schemes in the future without data loss
Implement versioned encryption and automatic re-encryption on unseal, as described in ARCHITECTURE.md section 4.2. The `schema_version` column exists on `aead_encrypted` but no migration logic is implemented. **Requirements:** - Define encryption scheme versions (starting with v1: ChaCha20-Poly1305) - On unseal, scan `aead_encrypted` for entries with `schema_version < current` - Re-encrypt outdated entries with the current scheme - Ensure re-encryption is atomic (no partial state on failure) - Support adding new encryption schemes in the future without data loss
Skipper added the
Kind
Feature
 label 2026-02-14 11:34:32 +00:00
Skipper added the
Difficulty
Medium
2
Priority
Medium
3
 labels 2026-02-14 11:44:17 +00:00
Skipper added the
Status
Abandoned
3
 label 2026-02-16 21:32:31 +00:00
Skipper commented 2026-02-16 21:32:45 +00:00
Author
Owner
Copy Link

Currently abandoned as no migration is required

Currently abandoned as no migration is required
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat
Breaking
Breaking change that won't be backward compatible
Difficulty
High
3
Hard difficulty. Experience needed to fix: A lot.
Difficulty
Low
1
Easy difficulty. Experience needed to fix: Not much. Good first issue.
Difficulty
Medium
2
Medium difficulty. Experience needed to fix: Intermediate.
Kind
Bug
This is a bug.
Kind
Enhancement
Improve existing functionality.
Kind
Feature
New functionality
Kind
RFC
Request for comments
Kind
Security
This is security issue
Kind
Testing
This is testing issue.
Kind
Tracking issue
An issue tracking the progress of sth. like the implementation of an RFC
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Pending
4
Requires review by dev
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Difficulty
Medium
2
Kind
Feature
Priority
Medium
3
Status
Abandoned
3
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
CleverWild Skipper goodvin testuser
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MarketTakers/arbiter#15
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?