Redis driver doesn't explicitly validate UUIDs
Bug #1367024 reported by
Kurt Griffiths
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
Low
|
Masaki Matsushita |
Bug Description
For claim and message IDs, as well as as client_uuids, the driver does not always validate that they are real UUIDs. This should not pose a problem, assuming redis-py sanitizes key names, but it would be good to do our own checking just to be certain.
Changed in zaqar: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in zaqar: | |
assignee: | nobody → Doraly Navarro (doralynavarro) |
Changed in zaqar: | |
assignee: | Doraly Navarro (doralynavarro) → aknksha (akanksha-dlf) |
Changed in zaqar: | |
assignee: | Akanksha Srivastava (akanksha-dlf) → nobody |
Changed in zaqar: | |
assignee: | nobody → Doraly Navarro (doralynavarro) |
Changed in zaqar: | |
assignee: | Doraly Navarro (doralynavarro) → Masaki Matsushita (glass-saga) |
Changed in zaqar: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
Changed in zaqar: | |
milestone: | liberty-2 → 1.0.0 |
To post a comment you must log in.
Should this be done as a falcon hook?