)]}'
{"specs/juno/multi-backend-uuids.rst":[{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"7fd919aacea236caa1639c4e868ca8395883b1a3","unresolved":false,"context_lines":[{"line_number":145,"context_line":"  being the default. The keys produced by generators will be limited to a"},{"line_number":146,"context_line":"  maximum string size 64 bytes (and any generator producing more than that"},{"line_number":147,"context_line":"  will cause an exception to be thrown)."},{"line_number":148,"context_line":"  "},{"line_number":149,"context_line":"  There are also several complexities that are created by creating an"},{"line_number":150,"context_line":"  identity mapping layer:"},{"line_number":151,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1ae5cdf2_7873dde6","line":148,"updated":"2014-06-19 21:37:17.000000000","message":"white space","commit_id":"8aa26f4377762ff5294cdabbcad9fa54dbacd89d"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"b33cfc3d337ac91ec8f5fd74a0d56a722f42c3b6","unresolved":false,"context_lines":[{"line_number":137,"context_line":"  The selection of a hash algorithm to use is a balance between resulting key"},{"line_number":138,"context_line":"  size (and hence column width of any client that will need to store the"},{"line_number":139,"context_line":"  generated ID), probability of collision and security of the encoded data."},{"line_number":140,"context_line":"  It should be noted that for most installations, the data being encrypted"},{"line_number":141,"context_line":"  here (local ID and domain ID) is not likely to considered secret - hence the"},{"line_number":142,"context_line":"  actual security of the hash involved is less important.  However, to"},{"line_number":143,"context_line":"  provide flexibility across all use cases, a pluggable generator backend"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_a4551fc3","line":140,"updated":"2014-06-20 22:11:04.000000000","message":"\"the data being encrypted\"? why are we encrypting local ID and domain ID?","commit_id":"4ae4d3d5ad5ad12ab8a18d4be3fcef65d85f70f6"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"f71d3c2242c0c399ae18dce6a49759d3cb7037fb","unresolved":false,"context_lines":[{"line_number":137,"context_line":"  The selection of a hash algorithm to use is a balance between resulting key"},{"line_number":138,"context_line":"  size (and hence column width of any client that will need to store the"},{"line_number":139,"context_line":"  generated ID), probability of collision and security of the encoded data."},{"line_number":140,"context_line":"  It should be noted that for most installations, the data being encrypted"},{"line_number":141,"context_line":"  here (local ID and domain ID) is not likely to considered secret - hence the"},{"line_number":142,"context_line":"  actual security of the hash involved is less important.  However, to"},{"line_number":143,"context_line":"  provide flexibility across all use cases, a pluggable generator backend"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_ad725b79","line":140,"in_reply_to":"1ae5cdf2_a4551fc3","updated":"2014-06-21 18:38:58.000000000","message":"Not encrypted, cryptologically secure hashing.\n\nLooks like the wrong phrasing","commit_id":"4ae4d3d5ad5ad12ab8a18d4be3fcef65d85f70f6"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"412930f2f37e2a6f63db0329c1006a30d26fa678","unresolved":false,"context_lines":[{"line_number":264,"context_line":"Further, if an unsupported identity mapping generator algorithm has been"},{"line_number":265,"context_line":"specified in the Keystone configuration file, then any identity API is likely"},{"line_number":266,"context_line":"to generate a 500 (Internal Server Error) return code."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Security Impact"},{"line_number":269,"context_line":"---------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_33df9767","line":267,"updated":"2014-06-20 19:45:06.000000000","message":"We talked about this is chat a little, but I think it would be important to add some more details to this section.\n\n - What is the real danger of using an insecure hashing algorithm? Even if it\u0027s secure now that could change.\n - It was mentioned that it may be possible to obtain access to groups by taking advantage of an insecure hashing algorithm. Provide a local id that hashes to the same public id and another local id. Is this possible? How probable is it and what can we do about it? I believe that this won\u0027t matter for users, but I\u0027ve been wrong once or twice :)","commit_id":"4ae4d3d5ad5ad12ab8a18d4be3fcef65d85f70f6"},{"author":{"_account_id":11045,"name":"Bob Thyne","email":"bob.thyne@hp.com","username":"bobt"},"change_message_id":"ef935c46907eb8faaae98cfe9f5bd562fa0c8792","unresolved":false,"context_lines":[{"line_number":264,"context_line":"Further, if an unsupported identity mapping generator algorithm has been"},{"line_number":265,"context_line":"specified in the Keystone configuration file, then any identity API is likely"},{"line_number":266,"context_line":"to generate a 500 (Internal Server Error) return code."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Security Impact"},{"line_number":269,"context_line":"---------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_b520e79a","line":267,"in_reply_to":"1ae5cdf2_33df9767","updated":"2014-06-21 01:44:41.000000000","message":"Regarding the danger of using an insecure hash algorithm. If it\u0027s important to have additional security information, I would add a reference to further reading. NIST has some good papers on the topic e.g.\n\nhttp://csrc.nist.gov/publications/nistpubs/800-107-rev1/sp800-107-rev1.pdf (in particular chapter #4)\n\nGeneral high level policy information on what to use and further links:\n\nhttp://csrc.nist.gov/groups/ST/hash/policy.html","commit_id":"4ae4d3d5ad5ad12ab8a18d4be3fcef65d85f70f6"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"f71d3c2242c0c399ae18dce6a49759d3cb7037fb","unresolved":false,"context_lines":[{"line_number":264,"context_line":"Further, if an unsupported identity mapping generator algorithm has been"},{"line_number":265,"context_line":"specified in the Keystone configuration file, then any identity API is likely"},{"line_number":266,"context_line":"to generate a 500 (Internal Server Error) return code."},{"line_number":267,"context_line":""},{"line_number":268,"context_line":"Security Impact"},{"line_number":269,"context_line":"---------------"},{"line_number":270,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1ae5cdf2_cd6de79a","line":267,"in_reply_to":"1ae5cdf2_b520e79a","updated":"2014-06-21 18:38:58.000000000","message":"I don\u0027t know if this extra info is needed in this spec. This seems like generally useful info, but - out of scope for the specification. It seems that the NIST documents cover this, maybe just a footnote reference?","commit_id":"4ae4d3d5ad5ad12ab8a18d4be3fcef65d85f70f6"},{"author":{"_account_id":6486,"name":"Brant Knudson","email":"blk@acm.org","username":"blk-u"},"change_message_id":"cf9ef4706af9e432c4b479073374b33447db4bb9","unresolved":false,"context_lines":[{"line_number":91,"context_line":"  identity mapping entries will be created, since there is only the single"},{"line_number":92,"context_line":"  standard identity driver. The only case where entity IDs from the standard"},{"line_number":93,"context_line":"  identity driver will be mapped is if the cloud provider wants to ensure that"},{"line_number":94,"context_line":"  the whatever LDAP attribute is being used as the entity ID is not exposed as"},{"line_number":95,"context_line":"  thePublic ID.  This is achieved by setting the ``backward_compatible_ids``"},{"line_number":96,"context_line":"  configuration option to ``False``."},{"line_number":97,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"1ae5cdf2_1bf35ce8","line":94,"updated":"2014-06-23 20:05:15.000000000","message":"remove \"the\" from \"the whatever\"","commit_id":"d29d014dab35b651e2c9b36423423ffa2b3d4362"},{"author":{"_account_id":6486,"name":"Brant Knudson","email":"blk@acm.org","username":"blk-u"},"change_message_id":"cf9ef4706af9e432c4b479073374b33447db4bb9","unresolved":false,"context_lines":[{"line_number":92,"context_line":"  standard identity driver. The only case where entity IDs from the standard"},{"line_number":93,"context_line":"  identity driver will be mapped is if the cloud provider wants to ensure that"},{"line_number":94,"context_line":"  the whatever LDAP attribute is being used as the entity ID is not exposed as"},{"line_number":95,"context_line":"  thePublic ID.  This is achieved by setting the ``backward_compatible_ids``"},{"line_number":96,"context_line":"  configuration option to ``False``."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"- Public ID generator algorithm."}],"source_content_type":"text/x-rst","patch_set":8,"id":"1ae5cdf2_fb1cf016","line":95,"updated":"2014-06-23 20:05:15.000000000","message":"add a space to \"the Public ID\"","commit_id":"d29d014dab35b651e2c9b36423423ffa2b3d4362"}]}
