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

[Feature] HTML report add option to report like on terminal (dark) #2462

Open
DSEyers opened this issue Jan 30, 2024 · 3 comments
Open

[Feature] HTML report add option to report like on terminal (dark) #2462

DSEyers opened this issue Jan 30, 2024 · 3 comments

Comments

@DSEyers
Copy link

DSEyers commented Jan 30, 2024

Would like the HTML report to look like the report that is printed to the screen.
That is would like black background etc. The whiteback ground is killing me!

@drwetter
Copy link
Owner

If you're still alive which I hope so: If this is a feature request, there would be also a template for that.

@drwetter drwetter changed the title HTML report add option to report like on terminal (dark) [Feature] HTML report add option to report like on terminal (dark) Feb 6, 2024
@dcooper16
Copy link
Contributor

We can't make the HTML "look like the report that is printed on the screen," because testssl.sh can not determine what your screen looks like. We could, however, have an option to make the HTML background black (or any other color).

If someone is interested in working on this, I would suggest starting by looking at #1518. Once you choose a background color (e.g., black), use the referenced tools to find colors that meet accessibility guidelines when displayed on the chosen background color. As I did in #1518, you can then present the set of colors here with an image showing what they look like, so that people can comment on them. Once the colors have been selected, writing the PR will be relatively easy.

@drwetter
Copy link
Owner

good hint @dcooper16 .

Other than specifying colors an alternative might be a cmd line option which specifies a CSS which is probably best to include inline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants