{"action":"created","issue":{"url":"https://api.github.com/repos/jvehent/cipherscan/issues/72","labels_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72/labels{/name}","comments_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72/comments","events_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72/events","html_url":"https://github.com/jvehent/cipherscan/issues/72","id":103460592,"number":72,"title":"Pick up openssl with complete -help message","user":{"login":"tomato42","id":618246,"avatar_url":"https://avatars.githubusercontent.com/u/618246?v=3","gravatar_id":"","url":"https://api.github.com/users/tomato42","html_url":"https://github.com/tomato42","followers_url":"https://api.github.com/users/tomato42/followers","following_url":"https://api.github.com/users/tomato42/following{/other_user}","gists_url":"https://api.github.com/users/tomato42/gists{/gist_id}","starred_url":"https://api.github.com/users/tomato42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tomato42/subscriptions","organizations_url":"https://api.github.com/users/tomato42/orgs","repos_url":"https://api.github.com/users/tomato42/repos","events_url":"https://api.github.com/users/tomato42/events{/privacy}","received_events_url":"https://api.github.com/users/tomato42/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-08-27T08:58:10Z","updated_at":"2015-09-01T12:35:20Z","closed_at":null,"body":"since now we can detect features of openssl s_client through -help message (see https://github.com/openssl/openssl/commit/a7cb67f4f2457724fbfbc39377f55c26f3aafa80 and https://github.com/openssl/openssl/commit/ad775e04f6dab51b7f929b54f5aa3c2393f957c5 for 1.0.2 and master patches) it will be possible to autodetect if we can do more advanced scanning.\r\n"},"comment":{"url":"https://api.github.com/repos/jvehent/cipherscan/issues/comments/136699128","html_url":"https://github.com/jvehent/cipherscan/issues/72#issuecomment-136699128","issue_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72","id":136699128,"user":{"login":"tomato42","id":618246,"avatar_url":"https://avatars.githubusercontent.com/u/618246?v=3","gravatar_id":"","url":"https://api.github.com/users/tomato42","html_url":"https://github.com/tomato42","followers_url":"https://api.github.com/users/tomato42/followers","following_url":"https://api.github.com/users/tomato42/following{/other_user}","gists_url":"https://api.github.com/users/tomato42/gists{/gist_id}","starred_url":"https://api.github.com/users/tomato42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tomato42/subscriptions","organizations_url":"https://api.github.com/users/tomato42/orgs","repos_url":"https://api.github.com/users/tomato42/repos","events_url":"https://api.github.com/users/tomato42/events{/privacy}","received_events_url":"https://api.github.com/users/tomato42/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T12:35:20Z","updated_at":"2015-09-01T12:35:20Z","body":"hash has the downside of requiring us to keep the binary repo/website in sync with the cipherscan repo... AFAIK, to verify gpg signatures you need the gpg certificate in local keyring\r\n\r\nso I think that hash would be better, but only if the download is fired when openssl in local directory is missing, not when the hash doesn't match (if someone wants new openssl, he or she just needs to delete or rename the one in the local directory)"}}