{"action":"created","issue":{"url":"https://api.github.com/repos/openssl/openssl/issues/6798","repository_url":"https://api.github.com/repos/openssl/openssl","labels_url":"https://api.github.com/repos/openssl/openssl/issues/6798/labels{/name}","comments_url":"https://api.github.com/repos/openssl/openssl/issues/6798/comments","events_url":"https://api.github.com/repos/openssl/openssl/issues/6798/events","html_url":"https://github.com/openssl/openssl/issues/6798","id":345063628,"node_id":"MDU6SXNzdWUzNDUwNjM2Mjg=","number":6798,"title":"provide an API for Certificate Transparency (CT rfc6962) retrieval using 1.0.2 line","user":{"login":"blshkv","id":309751,"node_id":"MDQ6VXNlcjMwOTc1MQ==","avatar_url":"https://avatars2.githubusercontent.com/u/309751?v=4","gravatar_id":"","url":"https://api.github.com/users/blshkv","html_url":"https://github.com/blshkv","followers_url":"https://api.github.com/users/blshkv/followers","following_url":"https://api.github.com/users/blshkv/following{/other_user}","gists_url":"https://api.github.com/users/blshkv/gists{/gist_id}","starred_url":"https://api.github.com/users/blshkv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blshkv/subscriptions","organizations_url":"https://api.github.com/users/blshkv/orgs","repos_url":"https://api.github.com/users/blshkv/repos","events_url":"https://api.github.com/users/blshkv/events{/privacy}","received_events_url":"https://api.github.com/users/blshkv/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-07-27T01:58:21Z","updated_at":"2018-07-27T11:31:31Z","closed_at":"2018-07-27T03:22:18Z","author_association":"NONE","body":"1.0.2j introduced a way to obtain CT information. However, unlike 1.1.1 this information is not available via APIs.  We are facing an issue with sslyze security tool which relies on cryptography and the problem reported in the bug report below:\r\nhttps://github.com/pyca/cryptography/issues/4373\r\n\r\nIt would be good if you could fix that.\r\n"},"comment":{"url":"https://api.github.com/repos/openssl/openssl/issues/comments/408392268","html_url":"https://github.com/openssl/openssl/issues/6798#issuecomment-408392268","issue_url":"https://api.github.com/repos/openssl/openssl/issues/6798","id":408392268,"node_id":"MDEyOklzc3VlQ29tbWVudDQwODM5MjI2OA==","user":{"login":"kroeckx","id":1616242,"node_id":"MDQ6VXNlcjE2MTYyNDI=","avatar_url":"https://avatars3.githubusercontent.com/u/1616242?v=4","gravatar_id":"","url":"https://api.github.com/users/kroeckx","html_url":"https://github.com/kroeckx","followers_url":"https://api.github.com/users/kroeckx/followers","following_url":"https://api.github.com/users/kroeckx/following{/other_user}","gists_url":"https://api.github.com/users/kroeckx/gists{/gist_id}","starred_url":"https://api.github.com/users/kroeckx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kroeckx/subscriptions","organizations_url":"https://api.github.com/users/kroeckx/orgs","repos_url":"https://api.github.com/users/kroeckx/repos","events_url":"https://api.github.com/users/kroeckx/events{/privacy}","received_events_url":"https://api.github.com/users/kroeckx/received_events","type":"User","site_admin":false},"created_at":"2018-07-27T11:31:31Z","updated_at":"2018-07-27T11:31:31Z","author_association":"MEMBER","body":"In Debian things like python, apache, wpasupplicant have all moved to 1.1.0.  This is the full list of packages that haven't moved to 1.1.0 yet in Debian testing:\r\nkopete\r\nnetty-tcnative\r\nopenssh\r\nwvstreams\r\n\r\nI guess I'll look into getting those 4 fixed the next few days."}}
{"actor":{"display_login":"kroeckx"}}