{"action":"opened","issue":{"url":"https://api.github.com/repos/jdauphant/ansible-role-ssl-certs/issues/18","repository_url":"https://api.github.com/repos/jdauphant/ansible-role-ssl-certs","labels_url":"https://api.github.com/repos/jdauphant/ansible-role-ssl-certs/issues/18/labels{/name}","comments_url":"https://api.github.com/repos/jdauphant/ansible-role-ssl-certs/issues/18/comments","events_url":"https://api.github.com/repos/jdauphant/ansible-role-ssl-certs/issues/18/events","html_url":"https://github.com/jdauphant/ansible-role-ssl-certs/issues/18","id":157554014,"number":18,"title":"ssl_certs_mode is not used for generated certs","user":{"login":"j4m3s","id":1998995,"avatar_url":"https://avatars.githubusercontent.com/u/1998995?v=3","gravatar_id":"","url":"https://api.github.com/users/j4m3s","html_url":"https://github.com/j4m3s","followers_url":"https://api.github.com/users/j4m3s/followers","following_url":"https://api.github.com/users/j4m3s/following{/other_user}","gists_url":"https://api.github.com/users/j4m3s/gists{/gist_id}","starred_url":"https://api.github.com/users/j4m3s/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/j4m3s/subscriptions","organizations_url":"https://api.github.com/users/j4m3s/orgs","repos_url":"https://api.github.com/users/j4m3s/repos","events_url":"https://api.github.com/users/j4m3s/events{/privacy}","received_events_url":"https://api.github.com/users/j4m3s/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-30T20:36:55Z","updated_at":"2016-05-30T20:36:55Z","closed_at":null,"body":"`ssl_certs_path_owner` and `ssl_certs_path_group` are also ignored, the generated certificate is left under the ownership of the ansible user.  \r\n\r\nI would have expected that these settings would be applied the same way to generated certificates as well as copied ones.\r\n\r\n(NB this applies to dhparam.pem too)."}}
{"actor":{"display_login":"j4m3s"}}