Skip to content

examples-docker.md

Latest commit

 

History

History
128 lines (95 loc) · 4.68 KB

examples-docker.md

File metadata and controls

128 lines (95 loc) · 4.68 KB
Raw

More Examples Of Running John The Ripper On Docker

Syntax

 # CPU and GPU formats
 docker run -it ghcr.io/openwall/john:latest <binary id> <john options>

 # To run ztex formats
 docker run --device=/dev/ttyUSB0 ghcr.io/openwall/john:v1.9.0J1 ztex <john options>

Basic usage

Using the --rm flag to clean up the container and remove the file system after the container exits.

 docker run --rm ghcr.io/openwall/john # => uses the best SIMD available, tag 'latest' can be omitted
 docker run --rm ghcr.io/openwall/john:bleeding # => uses the latest bleeding release
 docker run --rm ghcr.io/openwall/john:latest best # => uses the best SIMD available
 docker run --rm ghcr.io/openwall/john:latest avx2 --list=build-info
 docker run --rm ghcr.io/openwall/john:latest avx2-omp --list=build-info
 docker run --rm ghcr.io/openwall/john:latest avx512bw --test=0 --format=cpu

Run a real cracking session

 docker run ghcr.io/openwall/john:latest -list=format-tests | cut -f3 > ~/allTests.in
 docker run -v "$HOME":/host ghcr.io/openwall/john:latest avx2 --format=SHA512crypt /host/allTests.in --max-run=300

Run a real cracking session, saving the session information on the host

 # I'm using a demo hashes file:
 docker run ghcr.io/openwall/john:latest -list=format-tests | cut -f3 > allTests.in

 docker run -v "$(pwd)":/home/JtR ghcr.io/openwall/john best --format=SHA512crypt /home/JtR/allTests.in --max-run=30
 docker run -v "$(pwd)":/home/JtR ghcr.io/openwall/john best --format=SHA512crypt --wordlist --rules /home/JtR/allTests.in --max-run=20
 docker run -v "$(pwd)":/home/JtR ghcr.io/openwall/john best --format=SHA512crypt --incremental:digits /home/JtR/allTests.in --max-run=20

 # On the host (inside the current folder) I can find the session files:
 $ ls -lahR
 total 3,9G
 drwxrwxr-x  5 claudio users 4,0K jun 20 08:59  .
 drwxr-x--- 22 claudio users 4,0K jun 20 08:59  ..
 -rw-rw-r--  1 claudio users 1,2M jun 20 08:58  allTests.in
 drwx------  2 claudio users 4,0K jun 20 08:59  .john
 [...]
 ./.john:
 total 24K
 drwx------ 2 claudio users 4,0K jun 20 08:59 .
 drwxrwxr-x 5 claudio users 4,0K jun 20 08:59 ..
 -rw------- 1 claudio users 8,4K jun 20 08:59 john.log
 -rw------- 1 claudio users    0 jun 20 08:59 john.pot
 -rw------- 1 claudio users  246 jun 20 08:59 john.rec

Execute compiled 2john tools

It is possible to run some 2john tools directly from the Docker image. Example:

# If necessary, update the local Docker image
docker pull ghcr.io/openwall/john:bleeding

# To extract the relevant information from (e.g.) a zip file
docker run -v $(pwd):/host --rm -w /host --entrypoint /john/run/zip2john ghcr.io/openwall/john:bleeding /host/file.zip

# Or
docker run -v $(pwd):/host --rm -w /host --entrypoint /john/run/zip2john ghcr.io/openwall/john:bleeding /host/file.zip > zip.hash

The Docker image does not have Python or Lua installed, so it is not possible to run scripts using this approach.

Compare the performance of SIMD extensions

 docker run ghcr.io/openwall/john:latest avx      --test=10 --format=SHA512crypt
 docker run ghcr.io/openwall/john:latest avx2     --test=10 --format=SHA512crypt
 docker run ghcr.io/openwall/john:latest avx512bw --test=10 --format=SHA512crypt

Binaries

The available linux/amd64 binaries (their IDs are avx-omp, avx, etc) are:

  • /john/run/john-avx-omp (default binary)
  • /john/run/john-avx
  • /john/run/john-avx2-omp
  • /john/run/john-avx2
  • /john/run/john-avx512bw-omp
  • /john/run/john-avx512bw

The available linux/arm64 binaries (their IDs are omp and aarch64) are:

  • /john/run/john-omp (default binary)
  • /john/run/john-aarch64

Binaries available on Docker image John 1.9.0 Jumbo 1 (their IDs are ztex and ztex-no-omp) are:

  • /john/run/john-ztex (SSE2)
  • /john/run/john-ztex-no-omp (SSE2)

Docker image verification

Anyone can verify the Docker image using the commands below:

Simple and nice IMO:

$ ./cosign-linux-amd64 tree ghcr.io/openwall/john:latest
📦 Supply Chain Security Related artifacts for an image: ghcr.io/openwall/john:latest
└── 💾 Attestations for an image tag: ghcr.io/openwall/john:sha256-c9275acf784a3f19cab3ce0aab3cedefbe986dcbe70df650e5802ec23127f4da.att
   └── 🍒 sha256:e777d619092a02e919ebe242431df428369edc22e0ccbe0a9214678343452af8

A more detailed list of information:

$ ./cosign-linux-amd64 verify-attestation \
      --certificate-identity https://github.com/slsa-framework/slsa-github-generator/.github/workflows/generator_container_slsa3.yml@refs/tags/v1.7.0 \
      --certificate-oidc-issuer https://token.actions.githubusercontent.com \
      --type slsaprovenance \
    ghcr.io/openwall/john:latest
# a lot of info will be printed here