summaryrefslogtreecommitdiffstats
path: root/dom/crypto
Commit message (Collapse)AuthorAgeLines
* Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23-1/+0
|
* Issue #1656 - Part 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-9/+0
| | | | | | Since these are just interpreted comments, there's 0 impact on actual code. This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are a few others scattered around which will be removed manually in a second part.
* Issue #80 - Resolve issues with compiling on insane gcc configurations with ↵Matt A. Tobin2020-04-25-0/+1
| | | | no optimizations in dom/
* Issue #80 - De-unify dom/cryptowolfbeast2020-04-19-1/+5
|
* Root parameter dictionaries in AesTask::Init().wolfbeast2018-12-13-3/+3
|
* Remove all C++ Telemetry Accumulation calls.wolfbeast2018-09-03-40/+0
| | | | | This creates a number of stubs and leaves some surrounding code that may be irrelevant (eg. recorded time stamps, status variables). Stub resolution/removal should be a follow-up to this.
* Check for integer overflow in AesTask::DoCrypto() (DiD)wolfbeast2018-02-08-0/+5
| | | | | | | | | | | | 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.0Matt A. Tobin2018-02-02-0/+13414
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-27 12:41:51 +0000