{"action":"created","issue":{"url":"https://api.github.com/repos/letsencrypt/boulder/issues/1452","repository_url":"https://api.github.com/repos/letsencrypt/boulder","labels_url":"https://api.github.com/repos/letsencrypt/boulder/issues/1452/labels{/name}","comments_url":"https://api.github.com/repos/letsencrypt/boulder/issues/1452/comments","events_url":"https://api.github.com/repos/letsencrypt/boulder/issues/1452/events","html_url":"https://github.com/letsencrypt/boulder/issues/1452","id":130072618,"number":1452,"title":"Support CAA account key binding","user":{"login":"hlandau","id":2270010,"avatar_url":"https://avatars.githubusercontent.com/u/2270010?v=3","gravatar_id":"","url":"https://api.github.com/users/hlandau","html_url":"https://github.com/hlandau","followers_url":"https://api.github.com/users/hlandau/followers","following_url":"https://api.github.com/users/hlandau/following{/other_user}","gists_url":"https://api.github.com/users/hlandau/gists{/gist_id}","starred_url":"https://api.github.com/users/hlandau/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hlandau/subscriptions","organizations_url":"https://api.github.com/users/hlandau/orgs","repos_url":"https://api.github.com/users/hlandau/repos","events_url":"https://api.github.com/users/hlandau/events{/privacy}","received_events_url":"https://api.github.com/users/hlandau/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/letsencrypt/boulder/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-01-31T04:00:27Z","updated_at":"2016-02-03T00:34:33Z","closed_at":null,"body":"It would be nice if boulder supported a CAA record nominating an account key thumbprint via a parameter. This was envisioned by the CAA RFC.\r\n\r\nSomething like `IN CAA 0 issue \"letsencrypt.org; acme-ak=[base64url account key thumbprint]\"`."},"comment":{"url":"https://api.github.com/repos/letsencrypt/boulder/issues/comments/178914558","html_url":"https://github.com/letsencrypt/boulder/issues/1452#issuecomment-178914558","issue_url":"https://api.github.com/repos/letsencrypt/boulder/issues/1452","id":178914558,"user":{"login":"rolandshoemaker","id":5080674,"avatar_url":"https://avatars.githubusercontent.com/u/5080674?v=3","gravatar_id":"","url":"https://api.github.com/users/rolandshoemaker","html_url":"https://github.com/rolandshoemaker","followers_url":"https://api.github.com/users/rolandshoemaker/followers","following_url":"https://api.github.com/users/rolandshoemaker/following{/other_user}","gists_url":"https://api.github.com/users/rolandshoemaker/gists{/gist_id}","starred_url":"https://api.github.com/users/rolandshoemaker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rolandshoemaker/subscriptions","organizations_url":"https://api.github.com/users/rolandshoemaker/orgs","repos_url":"https://api.github.com/users/rolandshoemaker/repos","events_url":"https://api.github.com/users/rolandshoemaker/events{/privacy}","received_events_url":"https://api.github.com/users/rolandshoemaker/received_events","type":"User","site_admin":false},"created_at":"2016-02-03T00:34:33Z","updated_at":"2016-02-03T00:34:33Z","body":"Whoops, forgot to check that before giving you bad advice, my bad! Your new\nplan sounds good, UpdateValidations has been a sore spot in the past so\nsome refactoring would be greatly appreciated. Eventually we are planning\non moving towards gRPC instead of our homebrew system but this won't happen\nfor a while.\n\nOn Tue, Feb 2, 2016 at 4:29 PM Hugo Landau <notifications@github.com> wrote:\n\n> So on further inspection, it looks like CheckCAARecords isn't called\n> anywhere except in tests, where having it on the interface is unnecessary\n> since it's a *ValidationAuthorityImpl being used directly there.\n>\n> As far as I can tell, removing CheckCAARecords as an RPC call can be done\n> without consequence, without even a config flag, since nothing uses it via\n> RPC. All CAA checking is actually done via UpdateValidations.\n>\n> UpdateValidations will need to be changed, so I'll probably change it out\n> for something which takes a request structure, which will at least make\n> future expansion easier. Should probably considered desirable going\n> forward, RPC-wise...\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/letsencrypt/boulder/issues/1452#issuecomment-178909642>\n> .\n>\n"}}