Archived
volker.raschek
4af5fe070b
The workflows pulled tonistiigi/binfmt through an unauthenticated request, either directly from docker.io or from harbor.cryptic.systems before any credentials had been configured. Both variants are subject to upstream rate limiting and made the multi arch builds fail sporadically. The docker/login-action steps are now placed in front of docker/setup-qemu-action and docker/setup-buildx-action, and a second login against harbor.cryptic.systems was added so that the binfmt image is always pulled from the internal registry with valid credentials. Leftover setup-qemu-action and setup-buildx-action steps from the previous ordering were removed. All pinned actions were additionally bumped to their latest upstream release to remove the version drift between the repositories.
bruteforce-wallet-docker
This project contains all sources to build the container image git.cryptic.systems/volker.raschek/bruteforce-wallet.
The primary goal of this project is to package the binary bruteforce-wallet as container image to provide the
functionally for CI/CD workflows. The source code of the binary can be found in the upstream project of
bruteforce-wallet.
Usage
The following example mounts the file wallet.dat located in the same directory where the command is executed into the
container filesystem as /tmp/wallet.dat. We also set some additional options, such as the password starting with foo
and ending with bar. In addition, we know that the password consists only of lower case letters and is between 4 and 8
characters long.
docker run \
--rm \
--volume wallet.dat:/tmp/wallet.dat \
-b foo \
-e bar \
-s abcdefghijklmnopqrstuvwxyz \
-l 4 \
-m 8 \
/tmp/wallet.dat