diff options
| author | Thomas Kriechbaumer <thomas@kriechbaumer.name> | 2018-09-18 20:42:48 +0200 |
|---|---|---|
| committer | Thomas Kriechbaumer <thomas@kriechbaumer.name> | 2018-09-18 20:42:48 +0200 |
| commit | 73577eb607803c50dc73b6d2e6c44560e563c23b (patch) | |
| tree | a7b8816ff0f0b88935fa7c5e2038249b3b71081f /release | |
| parent | cf15da1ed5e319bcc8dac18cb9f76166ac0a50fa (diff) | |
| download | mitmproxy-73577eb607803c50dc73b6d2e6c44560e563c23b.tar.gz mitmproxy-73577eb607803c50dc73b6d2e6c44560e563c23b.tar.bz2 mitmproxy-73577eb607803c50dc73b6d2e6c44560e563c23b.zip | |
update docker security warning
Diffstat (limited to 'release')
| -rw-r--r-- | release/docker/README.md | 16 |
1 files changed, 10 insertions, 6 deletions
diff --git a/release/docker/README.md b/release/docker/README.md index e7c9ab59..4511a33a 100644 --- a/release/docker/README.md +++ b/release/docker/README.md @@ -35,13 +35,17 @@ For further details, please consult the mitmproxy [documentation](http://docs.mi # Tags -The available release tags can be seen [here](https://hub.docker.com/r/mitmproxy/mitmproxy/tags/). +The available release tags can be seen +[here](https://hub.docker.com/r/mitmproxy/mitmproxy/tags/). * `master` always tracks the git-master branch and represents the unstable development tree. * `latest` always points to the same image as the most recent stable release, including bugfix releases (e.g., `4.0.0` and `4.0.1`). * `X.Y.Z` tags contain the mitmproxy release with this version number. - - All packages, dependencies, and the base image that were available at the time of the mitmproxy release. - - We DO NOT update these images! Use at your own risk! - - These images MIGHT BE affected by potential security issues! - - Security issues that were made public AFTER the release MIGHT affect these images! -* `*-ARMv7` are images built for Raspbian / Raspberry Pi +* `*-ARMv7` are images built for Raspbian / Raspberry Pi systems. + +# Security Notice + +Dependencies in the Docker images are frozen on release, and can’t be updated in +situ. This means that we necessarily capture any bugs or security issues that +may be present. We don’t generally release new Docker images simply to update +dependencies (though we may do so if we become aware of a really serious issue). |