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.

Sign up for GitHub

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

Jump to bottom

Dehydrated devices: does not detect if another client changed the dehydration key in 4S #28760

Open
Tracked by #922
uhoreg opened this issue Dec 17, 2024 · 0 comments
Open
Tracked by #922

Dehydrated devices: does not detect if another client changed the dehydration key in 4S #28760

uhoreg opened this issue Dec 17, 2024 · 0 comments
Labels
A-E2EE A-E2EE-Dehydration O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto

Comments

@uhoreg
Copy link
Member

uhoreg commented Dec 17, 2024

Does not detect when another client saves a new dehydration key in 4S, so when it tries to rotate the dehydrated device, it will continue to use the old dehydration key, which means that it will be undecryptable.
@dosubot dosubot bot added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect labels Dec 17, 2024
@uhoreg uhoreg mentioned this issue Dec 17, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE A-E2EE-Dehydration O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@uhoreg