From 392be259a0f813c7663d6962823117fa313122b1 Mon Sep 17 00:00:00 2001 From: Andres Erbsen Date: Wed, 3 Aug 2016 11:44:51 -0400 Subject: Mention Barrett reduction opt. in crypto-defects.md --- crypto-defects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crypto-defects.md') diff --git a/crypto-defects.md b/crypto-defects.md index a39064468..33d0a7c95 100644 --- a/crypto-defects.md +++ b/crypto-defects.md @@ -17,5 +17,5 @@ appearing in our code. | [CVE-2006-4339](https://web.archive.org/web/20071010042708/http://www.imc.org/ietf-openpgp/mail-archive/msg14307.html) | RSA-PKCS-1 sig. verification | irrelevant | padding check | | [CVE-2014-3570](https://www.openssl.org/news/secadv/20150108.txt) | Bignum squaring | | | | [ref/sc25519.c:84](https://github.com/floodyberry/supercop/blob/master/crypto_sign/ed25519/ref/sc25519.c#L84) | x mod (order of Curve25519) | Barrett reduction (code is likely correct) | "XXX" comment | - +| [ic#237002094](https://github.com/mit-plv/fiat-crypto/pull/42#issuecomment-237002094) | Barrett reduction for p256 | 1 conditional subtraction instead of 2 | unkown if ok | Not covered in the above list: memory mismanagement (buffer overrun, use-after-free, uninitialized read, null dereference), timing attacks (branch, cache, instruction). While these issues are very important, there are good programming disciplines for avoiding them without verifying intricate details of the computation. -- cgit v1.2.3