#120 Private keys stored in pactfoundation/pact-cli docker image Issue created by atucznio Pre issue-raising checklist I have already (please mark the applicable with an

x

): • [ x] Upgraded to the latest version of the relevant libraries • [ x] Checked to see if the issue has already been raised • [ x] Created an executable example that demonstrates the issue using either: • a Dockerfile • a fork of https://github.com/pact-foundation/pact-ruby-standalone-e2e-example • a Git repository with a Travis or Appveyor (or similar) build • a gist with all the relevant code and full instructions on how to run it Dockerfile contains only

FROM pactfoundation/pact-cli:latest

Software versions • pact library: pactfoundation/pact-cli:latest docker image • pact-ruby-standalone: - • OS: - Expected behaviour Private keys NOT stored in image - security issue Actual behaviour Private keys stored in pactfoundation/pact-cli docker image Steps to reproduce Build docker image from https://hub.docker.com/r/pactfoundation/pact-cli/tags Relevent log files Security scans raised this issue pact-foundation/pact-ruby-standalone