2 commits

Author	SHA1	Message	Date
wolfbeast	b67e03dc90	Check for integer overflow in AesTask::DoCrypto() (DiD) ... 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.	2019-02-15 23:30:14 +08:00
Roy Tam	dcd9973243	import FIREFOX_52_6_0esr_RELEASE from mozilla-esr52 hg repo	2018-01-19 03:59:58 +08:00