[MONGOCRYPT-7] Key broker deduplication broken Created: 27/Jun/19 Updated: 28/Oct/23 Resolved: 28/Jun/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Kevin Albertson | Assignee: | Kevin Albertson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Build libmongocrypt library |
| Description |
|
The key broker acts as intermediary storage of keys for encrypting/decrypting a single operation. When markings are received in libmongocrypt, the key broker tracks all requested key ids and alt names. When key documents are received, some entries are deduplicated (because a key may have been requested by both id and alt name, or multiple alt names). Due to a bug in this logic, it was possible for the key broker to lose key entries, resulting in an encryption/decryption failure due to missing key. |
| Comments |
| Comment by Githook User [ 01/Jul/19 ] |
|
Author: {'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com'}Message: |
| Comment by Githook User [ 28/Jun/19 ] |
|
Author: {'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com'}Message: |
| Comment by Githook User [ 27/Jun/19 ] |
|
Author: {'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@mongodb.com'}Message: |