{"action":"created","issue":{"url":"https://api.github.com/repos/drwetter/testssl.sh/issues/148","labels_url":"https://api.github.com/repos/drwetter/testssl.sh/issues/148/labels{/name}","comments_url":"https://api.github.com/repos/drwetter/testssl.sh/issues/148/comments","events_url":"https://api.github.com/repos/drwetter/testssl.sh/issues/148/events","html_url":"https://github.com/drwetter/testssl.sh/issues/148","id":97095082,"number":148,"title":"How to make it silent?","user":{"login":"vitz3","id":2292880,"avatar_url":"https://avatars.githubusercontent.com/u/2292880?v=3","gravatar_id":"","url":"https://api.github.com/users/vitz3","html_url":"https://github.com/vitz3","followers_url":"https://api.github.com/users/vitz3/followers","following_url":"https://api.github.com/users/vitz3/following{/other_user}","gists_url":"https://api.github.com/users/vitz3/gists{/gist_id}","starred_url":"https://api.github.com/users/vitz3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vitz3/subscriptions","organizations_url":"https://api.github.com/users/vitz3/orgs","repos_url":"https://api.github.com/users/vitz3/repos","events_url":"https://api.github.com/users/vitz3/events{/privacy}","received_events_url":"https://api.github.com/users/vitz3/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-24T17:13:54Z","updated_at":"2015-07-24T20:09:53Z","closed_at":null,"body":"I wanted to use this tool (good work btw) in parallel across like a trillion hosts and ports. Unfortunately it appears this tool is chatty. No news is good news and the banner/version information after each run is extra noise to parse out. Is there a q flag or something missing by chance?"},"comment":{"url":"https://api.github.com/repos/drwetter/testssl.sh/issues/comments/124701268","html_url":"https://github.com/drwetter/testssl.sh/issues/148#issuecomment-124701268","issue_url":"https://api.github.com/repos/drwetter/testssl.sh/issues/148","id":124701268,"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-07-24T20:09:53Z","updated_at":"2015-07-24T20:09:53Z","body":"> I wanted to use this tool (good work btw) \r\n\r\n(thx, appreciated)\r\n\r\n>  in parallel across like a trillion hosts and ports. Unfortunately it appears this tool is chatty. \r\n> No news is good news and the banner/version information after each run is extra noise to parse \r\n> out. Is there a q flag or something missing by chance?\r\n\r\nNot yet/ But it's a good idea If I do testing I help myself with\r\n``` \r\n./testssl.sh --sneaky --warnings batch --ip=one $* $hname | sed '/#########################################################/,/platform: \"linux-x86_64\")/d'\r\n```\r\n\r\nwhich filters the banner. I am redirecting the output anyway to e.g. have the possibility to do a diff or do other things/\r\n\r\nIn fact that filtering done by sed above can be easier achieved by ``-q``. That's not a bug deal and I can do that in the near future. More -- i.e. showing only negative results -- needs more consideration.\r\n\r\nIn mid terms I had in mind for mass testing to read the commands from a file and just have one banner. No big deal too. But not in the next two weeks or so."}}