)]}'
{"specs/liberty/approved/enable-password-complexity-checks.rst":[{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"dd68734c3e84f99b3490ee05ded36950b1c75419","unresolved":false,"context_lines":[{"line_number":24,"context_line":"uses two password symbol groups: default and easier, the default symbol group"},{"line_number":25,"context_line":"contains numbers, upper case letters and small case letters. the easier symbol"},{"line_number":26,"context_line":"group contains only numbers and upper case letters. The generated password is"},{"line_number":27,"context_line":"not complex enough and also can cause security problems."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Use Cases"},{"line_number":30,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_e3e0cffc","line":27,"updated":"2015-06-16 08:57:18.000000000","message":"IIUC, you are talking here about the admin password injected into the guest instance the user owns.\n\nI can see that openstack (keystone) should care about the strengh of passwords used for authentication with openstack services themselves, but I\u0027m not really convinced that openstack should be dictating password strength for users\u0027 own instances. Each organizations will already typically have their own requirements around password strength, and imposing some in the cloud too may well result in conflicting / contradictory policies. \n\nAs a general point, I think OpenStack should stay away from telling users what policies to use for stuff inside their instances, as I consider such policies to be upto the user to decide, not the cloud to impose.","commit_id":"79c803a59d86f366054fe5135baaa84d0e776044"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"dd68734c3e84f99b3490ee05ded36950b1c75419","unresolved":false,"context_lines":[{"line_number":83,"context_line":"Security impact"},{"line_number":84,"context_line":"---------------"},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"None"},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Notifications impact"},{"line_number":89,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa32b979_2386b765","line":86,"updated":"2015-06-16 08:57:18.000000000","message":"Err, this entire spec is about addressing security characteristics","commit_id":"79c803a59d86f366054fe5135baaa84d0e776044"}]}