Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transit - drop support for pre-v0.6.2 keys #37

Closed
cipherboy opened this issue Jan 6, 2024 · 0 comments · Fixed by #85
Closed

Transit - drop support for pre-v0.6.2 keys #37

cipherboy opened this issue Jan 6, 2024 · 0 comments · Fixed by #85
Labels
enhancement New feature or request

Comments

@cipherboy
Copy link
Member

In #36 (comment), it was mentioned again that Transit <v0.6.2 convergent encryption keys are weak (and the v2 convergent encryption scheme was as well, though less so). We should consider fully removing support for these operations so we can avoid a repeat of the vulnerability that occurred as a result of this old code paths being supported.

This probably warrants a bigger discussion about deprecation paths. This version is very old, upstream has not supported it for years, but yet the one-shot upgrade path (and necessity to decrypt existing data and prevent workflow breakage) has caused support to remain.

@naphelps naphelps added enhancement New feature or request feature and removed feature labels Jan 10, 2024
cipherboy pushed a commit to cipherboy/openbao that referenced this issue Jan 21, 2024
Build with go 1.21.3, and update related packages. Pin github actions
to the latest trusted versions, and test with k8s 1.24-1.28 and Vault
1.15.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants