https://github.com/captain-kark/dockerfile-veracode-gpg
A docker image for encrypting files to be communicated securely with veracode.
https://github.com/captain-kark/dockerfile-veracode-gpg
docker docker-image gpg public-key-encryption veracode
Last synced: about 2 months ago
JSON representation
A docker image for encrypting files to be communicated securely with veracode.
- Host: GitHub
- URL: https://github.com/captain-kark/dockerfile-veracode-gpg
- Owner: captain-kark
- License: mit
- Created: 2019-08-29T08:23:34.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-08-29T08:31:24.000Z (almost 7 years ago)
- Last Synced: 2025-04-12T16:13:47.046Z (about 1 year ago)
- Topics: docker, docker-image, gpg, public-key-encryption, veracode
- Language: Dockerfile
- Homepage: https://hub.docker.com/r/captainkark/veracode-gpg
- Size: 3.91 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
The document to encrypt should be mounted into the `/tmp/encrypt` directory of the container. The resulting `.gpg` file to share with veracode will appear next to it once the container terminates.
```
docker run --rm -it -v "${PWD}/encrypt/:/tmp/encrypt/" captainkark/veracode-gpg /tmp/encrypt/foobar.txt
```
Afterwards, on the host machine:
```
$: ls -A1 encrypt/
foobar.txt
foobar.txt.gpg
```
You can attach `foobar.txt.gpg` to an email (or whatever) to communicate secrets with veracode.
The public key that comes baked into the image can be verified, if desired.
```
$: docker run --rm -it --entrypoint gpg captainkark/veracode-gpg --list-keys
```
Which should output the following:
```
/root/.gnupg/pubring.kbx
------------------------
pub rsa2048 2012-04-24 [SC]
58F651DCBE9A644A8C01A485A56B91234E651127
uid [ unknown] Veracode MPT Team ⟨mpt@veracode.com⟩
sub rsa2048 2012-04-24 [E]
```