{"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":8,"created_at":"2015-08-27T08:58:10Z","updated_at":"2015-09-01T05:15:59Z","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/136589468","html_url":"https://github.com/jvehent/cipherscan/issues/72#issuecomment-136589468","issue_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72","id":136589468,"user":{"login":"drwetter","id":8036727,"avatar_url":"https://avatars.githubusercontent.com/u/8036727?v=3","gravatar_id":"","url":"https://api.github.com/users/drwetter","html_url":"https://github.com/drwetter","followers_url":"https://api.github.com/users/drwetter/followers","following_url":"https://api.github.com/users/drwetter/following{/other_user}","gists_url":"https://api.github.com/users/drwetter/gists{/gist_id}","starred_url":"https://api.github.com/users/drwetter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drwetter/subscriptions","organizations_url":"https://api.github.com/users/drwetter/orgs","repos_url":"https://api.github.com/users/drwetter/repos","events_url":"https://api.github.com/users/drwetter/events{/privacy}","received_events_url":"https://api.github.com/users/drwetter/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T05:15:59Z","updated_at":"2015-09-01T05:15:59Z","body":"\n\nAm 31. August 2015 22:09:10 MESZ, schrieb Peter Mosmans <notifications@github.com>:\n>So theoretically we could create a repo containing the binaries, and a\n>small bash installer/update/download script for the correct binary,\n>right ? A link to that installer script is then all that's needed for\n>people to grab their favorite openssl build and start scanning...\n>That way no one needs to clone the repo containing the binaries, so\n>testssl.sh and cipherscan will get a smaller footprint.\n\nThe problem for me is not one set of binaries but if it changes. Then the repo becomes fat and fatter.\n\nA downloader site has the problem for me that some users just don't use it. Don't know whether I should care but sometimes it costs my time ;)\n\nSorry about the question but I was just wondering whether there's no possibility to just purge old binaries from github. \n\nCheers, Dirk\n\n\n\n"}}