| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Check for integer overflow in AesTask::DoCrypto() (DiD) | wolfbeast | 2018-02-08 |
| | | | | | | | | | | | | | After calling mResult.SetLength(mData.Length() + 16) we should check that the integer addition didn't overflow. It seems at the moment impossible to create ArrayBuffers of size >= 0x0xfffffff0, however adding a check here doesn't hurt. mResult.Length() is passed to the PK11 API functions as a maxOut parameter and should be checked by the softoken crypto algorithm implementations. AES-ECB and AES-GCM seem to do that correctly. | ||
| * | Add m-esr52 at 52.6.0 | Matt A. Tobin | 2018-02-02 |
 |
index : uxp | |
| uxp [Local Fork] | khronosschoty@posteo.org |
| summaryrefslogtreecommitdiff |