2017-03-30 14:41:46 +02:00
## Usage:
2018-02-08 21:06:19 +01:00
( in git directory) :
2017-03-30 14:41:46 +02:00
` ` `
2018-02-08 21:06:19 +01:00
docker build -t mytestssl .
docker run -t mytestssl example.com
2017-03-30 14:41:46 +02:00
` ` `
2018-02-08 21:06:19 +01:00
You can also supply command line options like:
` ` docker run -t mytestssl -p --header example.com` `
2019-09-13 10:54:18 +02:00
or pull the image from dockerhub and run:
2019-08-14 17:50:29 +02:00
` ` `
2019-09-13 10:54:18 +02:00
docker run -t drwetter/testssl.sh --pfs example.com
` ` `
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` ` .
2019-08-14 17:50:29 +02:00
2019-09-13 10:54:18 +02:00
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.
2018-02-08 21:06:19 +01:00
2019-09-13 10:54:18 +02:00
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.:
2018-02-08 21:06:19 +01:00
2017-03-30 14:41:46 +02:00
` ` `
2019-09-13 10:54:18 +02:00
docker run -t -v /tmp:/data drwetter/testssl.sh --htmlfile /data/ example.com
2017-03-30 14:41:46 +02:00
` ` `
2017-11-19 16:48:05 +01:00
2019-09-13 10:54:18 +02:00
Also if you don't provide a user, testssl.sh' s docker container uses a non-root user ( usually with user/groupid 1000:1000) .