Last modified: 2014-01-21 23:39:21 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40860, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38860 - security@mediawiki.org : Create a public key and publish it on the public key servers
security@mediawiki.org : Create a public key and publish it on the public key...
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-30 18:40 UTC by T. Gries
Modified: 2014-01-21 23:39 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description T. Gries 2012-07-30 18:40:14 UTC
For submitting information to security@mediawiki.org a public key is missing. 

I suggest the creation of such a key and the publication on the key servers and of key and fingerprint on https://www.mediawiki.org/wiki/Manual:Security .
Comment 1 Krinkle 2012-07-31 08:53:16 UTC
(see also https://secure.wikimedia.org/keys.html)
Comment 2 Bawolff (Brian Wolff) 2012-07-31 19:08:57 UTC
/me notes these aren't exactly state secrets. I highly doubt we have to worry about someone intercepting emails to learn about an XSS attack on Wikipedia. That said , it doesn't really hurt anything to have such keys available for the paranoid.
Comment 3 T. Gries 2012-07-31 19:52:41 UTC
I say: one can never know what will happen (see FLAME). I did not say that all mails must be sent encrypted. I just proposed to have a public key available in case that someone prefers to sent their mail encrypted.
Comment 4 Bawolff (Brian Wolff) 2012-07-31 19:58:50 UTC
Well if someone with the resources to create something on the scale of the flame malware decides to start hating on us, we probably have larger problems ;)

Nonetheless, it certainly doesn't hurt to have such a key available.
Comment 5 Andre Klapper 2013-02-26 20:38:01 UTC
CC'ing Chris as this is security related. 

Chris: Any comments?
Comment 6 Chris Steipp 2013-02-26 22:52:29 UTC
I think it would be good to have a public key for this use. It's a pretty common practice, and almost no cost to us. Just need someone to generate the keys, distribute them, and post the public part in a few places.
Comment 7 Andre Klapper 2013-02-28 00:14:27 UTC
Plus key should probably be on http://www.mediawiki.org/wiki/Security .
For reference, https://www.mozilla.org/security/#pgpkey
Comment 8 Chris Steipp 2014-01-21 21:07:31 UTC
This would pretty much require a shared private key by everyone on the security@ mailing list, so we should also post disclaimers that it's only for encryption, and shouldn't be relied on for signatures.

Should someone generate a key and distribute it?
Comment 9 T. Gries 2014-01-21 23:39:21 UTC
(In reply to comment #8)
> This would pretty much require a shared private key by everyone on the
> security@ mailing list, so we should also post disclaimers that it's only for
> encryption, and shouldn't be relied on for signatures.

You can do this (1, 2, 1+2):

1. (recommended)
You can give a longer meaningful and describing name and/or comment, like

"Wikimedia/MediaWiki/Wikipedia Information Security Team - read by several persons <security@mediawiki.org>"

, and you could enumerate all team members by their name, in the comment field.


2. (optional, but requires all InfoSec team members to create an own key)
You can sign the "community key" by every team member, so that it is clear, who is member.

try gpg --gen-key to generate a test key, notice the optional comment field!


Sorry: I tried, but I couldn't find the maximum key comment field length.


The uploading to the keyservers is optional, the most important thing is that you publish the key and the fingerprint on a safe mediawiki site.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links