From fe87f8d6707e13fb9416d8e4c1ebc01817d53755 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Sun, 27 Jul 2014 13:48:59 +0200 Subject: [PATCH] Update from key ID in security.txt to authorized release keys list. --- docs/internals/security.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/internals/security.txt b/docs/internals/security.txt index 6d53c3dff7..e50696db1f 100644 --- a/docs/internals/security.txt +++ b/docs/internals/security.txt @@ -223,7 +223,14 @@ 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; +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 + + +same key used to sign Django releases; that key has the ID ``0x3684C0C08C8B2AE1``, and is available from most commonly-used keyservers.