1532292 - Treat signed S/MIME messages that use a SHA1 digest as insecure

Status: RESOLVED FIXED

(MailNews Core :: Security: S/MIME, enhancement)

Description

[Kai Engert (:KaiE:)]

Let's see when we can treat signed S/MIME messages that use a SHA1 digest as insecure.

Comment 1

[Magnus Melin [:mkmelin]]

https://en.wikipedia.org/wiki/SHA-1:
"Since 2005, SHA-1 has not been considered secure against well-funded opponents;[11] as of 2010 many organizations have recommended its replacement.[12][9][13] NIST formally deprecated use of SHA-1 in 2011 and disallowed its use for digital signatures in 2013"

Comment 2

[Kai Engert (:KaiE:)]

Attachment: Bug 1532292 - Reject S/MIME signatures that use the SHA-1 hash algorithm. r=mkmelin

Depends on D166957

Comment 3

[Magnus Melin [:mkmelin]]

Ready to land?

Comment 4

[Kai Engert (:KaiE:)]

My thinking was, let's Beta 112 have reject MD5, only, and let's reject SHA1 in 113.
This way we could more easily distinguish if someone is affected by MD5 or SHA1.

Comment 5

[Geoff Lankow (:darktrojan)]

This doesn't apply properly, even if I convince moz-phab not to download the earlier patch in the stack which has already landed.

Comment 6

[Kai Engert (:KaiE:)]

Ok sorry, thanks for trying, there was a whitespace fix in the base patch.

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/4dd8587a0684
Reject S/MIME signatures that use the SHA-1 hash algorithm. r=mkmelin