summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames Bennett <james@b-list.org>2014-07-27 13:55:40 +0200
committerJames Bennett <james@b-list.org>2014-07-27 13:55:40 +0200
commitdf55a697b39223dc183f3660a435c61e6aea84d5 (patch)
tree2be00552c25bb3c89dc8faa0168bec480b1f532f
parent99c2c917c3f859f2cc3fc1f7d5abb72730aa6c48 (diff)
[1.7.x] Update from key ID in security.txt to authorized release keys list.
Backport of fe87f8d6707e13fb9416d8e4c1ebc01817d53755 from master.
-rw-r--r--docs/internals/security.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/internals/security.txt b/docs/internals/security.txt
index 6d53c3dff7..20ab81a8ab 100644
--- a/docs/internals/security.txt
+++ b/docs/internals/security.txt
@@ -223,7 +223,9 @@ discretion of the Django development team, and that this privilege can
be revoked at any time, with or without explanation.
If you are added to the notification list, security-related emails
-will be sent to you by Django's release manager, and all notification
-emails will be signed with the same key used to sign Django releases;
-that key has the ID ``0x3684C0C08C8B2AE1``, and is available from most
-commonly-used keyservers.
+will be sent to you by Django's release team, and all notification
+emails will be signed with a key authorized to issue Django
+releases. The list of authorized keys is in `the Django releasers
+file`_.
+
+.. _the Django releasers file: https://www.djangoproject.com/m/pgp/django-releasers.txt