)]}'
{"reference/programs.yaml":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"a55209cba116c8b7f8a12401dd1a570c83f2687a","unresolved":false,"context_lines":[{"line_number":319,"context_line":"  codename: Barbican"},{"line_number":320,"context_line":"  ptl: Jarret Raim (jraim)"},{"line_number":321,"context_line":"  mission:"},{"line_number":322,"context_line":"    To produce an OpenStack key management API that simplifies the creation, management"},{"line_number":323,"context_line":"    and use of keying material for encryption purposes. We plan to achieve this by creating"},{"line_number":324,"context_line":"    and maintaining a Python service, libraries and documentation as well as working with"},{"line_number":325,"context_line":"    other OpenStack projects to enable encryption features for their customers and"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"AAAAVn%2F%2Fpus%3D","line":322,"updated":"2014-03-04 20:52:51.000000000","message":"Saying \"OpenStack\" is redundant. Saying \"simplifies\" is a bit of superfluous marketing. The description of the plan is useful, but not in the mission statement. How about shortening this to:\n\n  To produce an encryption key management service.\n\nI\u0027m not sure if the \"use of keying material for encryption purposes\" means that barbican is going to also perform the encryption. Is it?","commit_id":"425cfaf1534de39d7d81e9cf6a11ea32755c8c2b"},{"author":{"_account_id":7789,"name":"John Wood","email":"john.wood@rackspace.com","username":"woodster"},"change_message_id":"0fa3bcbf557bcb94f1786cf62f99d3db2a80046c","unresolved":false,"context_lines":[{"line_number":319,"context_line":"  codename: Barbican"},{"line_number":320,"context_line":"  ptl: Jarret Raim (jraim)"},{"line_number":321,"context_line":"  mission:"},{"line_number":322,"context_line":"    To produce an OpenStack key management API that simplifies the creation, management"},{"line_number":323,"context_line":"    and use of keying material for encryption purposes. We plan to achieve this by creating"},{"line_number":324,"context_line":"    and maintaining a Python service, libraries and documentation as well as working with"},{"line_number":325,"context_line":"    other OpenStack projects to enable encryption features for their customers and"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"AAAAVn%2F%2FbuY%3D","line":322,"in_reply_to":"AAAAVn%2F%2Fpus%3D","updated":"2014-03-06 04:27:21.000000000","message":"Hello Doug, to clarify, Barbican can securely store a client\u0027s keying material used for their encryption processes. The client could use that key to encrypt a disk volume (for example) outside of Barbican. Barbican does use encryption to secure the information it stores (via the HSM if enabled).\n\nWe\u0027ll send up a patch to address your review, thank you.","commit_id":"425cfaf1534de39d7d81e9cf6a11ea32755c8c2b"}]}