{"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":12,"created_at":"2015-08-27T08:58:10Z","updated_at":"2015-09-01T19:28:06Z","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/136834277","html_url":"https://github.com/jvehent/cipherscan/issues/72#issuecomment-136834277","issue_url":"https://api.github.com/repos/jvehent/cipherscan/issues/72","id":136834277,"user":{"login":"PeterMosmans","id":1465302,"avatar_url":"https://avatars.githubusercontent.com/u/1465302?v=3","gravatar_id":"","url":"https://api.github.com/users/PeterMosmans","html_url":"https://github.com/PeterMosmans","followers_url":"https://api.github.com/users/PeterMosmans/followers","following_url":"https://api.github.com/users/PeterMosmans/following{/other_user}","gists_url":"https://api.github.com/users/PeterMosmans/gists{/gist_id}","starred_url":"https://api.github.com/users/PeterMosmans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PeterMosmans/subscriptions","organizations_url":"https://api.github.com/users/PeterMosmans/orgs","repos_url":"https://api.github.com/users/PeterMosmans/repos","events_url":"https://api.github.com/users/PeterMosmans/events{/privacy}","received_events_url":"https://api.github.com/users/PeterMosmans/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T19:28:06Z","updated_at":"2015-09-01T19:28:06Z","body":"@jvehent, I don't have any issues with uploading binaries for OSX, linux(x86, x64) and Windows - as long as the server/bandwidth load stays within certain limits. How shall I distribute the hashes ? Create pull requests for cipherscan as well as testssl.sh ?\r\n@drwetter would you be okay with this generic approach ?\r\nIt would be ideal if both tools would support this new mechanism.\r\n\r\nSorry for hijacking this thread @tomato42, but looking at the mail conversations at openssl-dev it seems that the current core OpenSSL team is more interested in stability and ripping out \"old\" ciphers than supporting the highest number of ciphers. I thought the fork would be temporary, but as I see it now a 'feature-completer' version of OpenSSL might come in handy longer after all. Should I rename the fork to OpenSSL-swiss-army-knife-edition ? ;)"}}