Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2025-10-31 13:55:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

Housekeeping

Browse Source 
* add --rm
* better description of output
This commit is contained in:
Dirk Wetter
2019-11-27 09:49:51 +01:00
committed by GitHub
parent 9ce04a6219
commit 8e563e5361
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Dockerfile.md
View File

@@ -3,29 +3,32 @@
(in git directory): (in git directory):
``` ```
docker build -t mytestssl . docker build -t mytestssl .
docker run -t mytestssl example.com docker run --rm -t mytestssl example.com
``` ```
You can also supply command line options like: You can also supply command line options like:
``docker run -t mytestssl -p --header example.com`` ```
docker run -t mytestssl --help
docker run --rm -t mytestssl -p --header example.com
```
or pull the image from dockerhub and run: or pull the image from dockerhub and run:
``` ```
docker run -t drwetter/testssl.sh --pfs example.com docker run --rm -t drwetter/testssl.sh --pfs example.com
``` ```
Tags supported are: ``latest``, ``stable`` which _for now_ are all the same and point to ``3.0``. Tags supported are: ``latest``, ``stable`` which _for now_ are all the same and point to ``3.0``.
``docker run -t drwetter/testssl.sh:stable example.com``. ``docker run --rm -t drwetter/testssl.sh:stable example.com``.
And for the indomitable users who prefer to run old stuff you can use the tag ``2.9.5``. Please note ``2.9dev`` should not be used anymore. And for the indomitable users who prefer to run old stuff you can use the tag ``2.9.5``. Please note ``2.9dev`` should not be used anymore.
Keep in mind that any output file (--log, --html, --json etc.) will be created in the container. If you wish to have this created in a local directory you can mount a volume into the container and change the output prefix where the container user has write access to, e.g.: Keep in mind that any output file (--log, --html, --json etc.) will be created in the container. If you wish to have this created in a local directory you can mount a volume into the container and change the output prefix where the container user has write access to, e.g.:
``` ```
docker run -t -v /tmp:/data drwetter/testssl.sh --htmlfile /data/ example.com docker run --rm -t -v /tmp:/data drwetter/testssl.sh --htmlfile /data/ example.com
``` ```
Also if you don't provide a user, testssl.sh's docker container uses a non-root user (usually with user/groupid 1000:1000). which writes the output to ``/tmp/example.com_p443-<date>-<time>.html.`` The uid/gid is the one from the docker user but normally the file is 644. testssl.sh's docker container uses a non-root user (usually with user/groupid 1000:1000).