Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content checks should be less verbose #11

Closed
jcran opened this issue Sep 15, 2019 · 1 comment
Closed

Content checks should be less verbose #11

jcran opened this issue Sep 15, 2019 · 1 comment

Comments

@jcran
Copy link
Member

jcran commented Sep 15, 2019

See #8 as well, but this sort of verbosity around content checks is unnecessary. Save it for the JSON/CSV output. For the CLI, only print stuff that would be useful to a tester.

Specifically:

  • remove location header
  • remove security header info if they don't print something that can be actioned
  • remove anything that's 'false'
  • remove email addresses output if there are none.
Checking URL: http://127.0.0.1/
Checking... http://127.0.0.1/
Fingerprint:
 - Apache HTTP Server 2.4.41  - Apache web server - server header - with versions (CPE: cpe:2.3:a:apache:http_server:2.4.41:) (Tags: ["Web Server"])
Content Checks:
 - Access-Control-Allow-Origin Header: false
 - P3P Header: false
 - X-Frame-Options Header: false
 - X-XSS-Protection Header: false
 - Google Analytics Account Detected: false
 - Location Header: 
 - Directory Listing Detected: false
 - Form Detected: false
 - File Upload Form Detected: false
 - Email Addresses Detected: []
 - Authentication - HTTP: false
 - Authentication - Session Identifier: false````

via @bcoles 
@jcran
Copy link
Member Author

jcran commented Mar 28, 2020

CAlling this done

@jcran jcran closed this as completed Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant