From f6a4e7a3a68b29573bc7fcbfee249f31dce22613 Mon Sep 17 00:00:00 2001
From: Abhilash Raj <maxking@users.noreply.github.com>
Date: Fri, 12 Jun 2020 20:01:08 -0700
Subject: [PATCH] We don't really do image signing anymore. (#380)

Remove security tags from docs.
---
 README.md | 23 -----------------------
 1 file changed, 23 deletions(-)

diff --git a/README.md b/README.md
index 74a98fd..03279d8 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,6 @@ Table of Contents
    * [GNU Mailman 3 Deployment with Docker](#gnu-mailman-3-deployment-with-docker)
    * [Release](#release)
    * [Rolling Releases](#rolling-releases)
-      * [Security](#security)
    * [Dependencies](#dependencies)
    * [Configuration](#configuration)
       * [Mailman-web](#mailman-web)
@@ -116,28 +115,6 @@ $ docker inspect --format '{{json .Config.Labels }}' mailman-web | python -m jso
 - `version.postorius`: The commit hash of Postorius.
 - `version.dj-mm3`: The commit hash of Django-Mailman3 project.
 
-Security
---------
-
-All the releases are signed and can be verified using [Docker Content
-Trust][14]. To make sure that your docker client actually verifies these
-signatures, you can enable Docker's content trust by setting an environment
-variable `DOCKER_CONTENT_TRUST`. In bash/zsh you can try this:
-
-```bash
-$ export DOCKER_CONTENT_TRUST=1
-```
-
-Or, alternatively, you can do this on a per-command basis without setting the
-environment variable above. For example, when pulling an image:
-
-```bash
-$ docker pull --disable-content-trust=false maxking/mailman-core:release
-```
-
-The above command will fail if the release tag doesn't exist or is not signed.
-
-
 Dependencies
 ============
 - Docker