© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
That was my take as well, just being cautious. Considering that the Hash is generated by an operation completely controlled by Keystone, I don't think it is possible to intentionally create a collision on the server. In auth_token middleware, the Hash is based on a PKI verified token, so, again, a random document will never be hashed. Thus, this is a hardening issue.