summaryrefslogtreecommitdiffstats
path: root/security/nss/lib
Commit message (Collapse)AuthorAgeLines
* Issue #1338 - Follow-up: Also cache the most recent PBKDF1 hashKai Engert2020-01-23-50/+140
| | | | This rewrites the caching mechanism to apply to both PBKDF1 and PBKDF2
* Issue #1338 - Bump NSS versionwolfbeast2020-01-20-3/+3
| | | | | | | Our NSS version is closer to the currently-released .1, so bump version to that. Note: we still have some additional patches to the in-tree version in place so this isn't a 100% match to the RTM one.
* Issue #1338: Follow-up: Cache the most recent PBKDF2 password hash,Kai Engert2020-01-14-1/+83
| | | | | | to speed up repeated SDR operations. Landed on NSS-3.48 for Bug 1606992
* Issue #1338 - Followup: certdb: propagate trust information if trustDaiki Ueno2020-01-10-8/+22
| | | | | | | | | | | | | module is loaded afterwards, Summary: When the builtin trust module is loaded after some temp certs being created, these temp certs are usually not accompanied by trust information. This causes a problem in UXP as it loads the module from a separate thread while accessing the network cache which populates temp certs. This change makes it properly roll up the trust information, if a temp cert doesn't have trust information.
* Issue #1338 - Part 2: Update NSS to 3.48-RTMwolfbeast2020-01-02-28573/+80931
|
* Update NSS version.wolfbeast2019-12-06-6/+6
|
* [NSS] Bug 1586176 - EncryptUpdate should use maxout not block size.Craig Disselkoen2019-12-06-1/+1
|
* [NSS] Bug 1508776 - Remove unneeded refcounting from SFTKSessionJ.C. Jones2019-12-06-23/+11
| | | | | | | | SFTKSession objects are only ever actually destroyed at PK11 session closure, as the session is always the final holder -- and asserting refCount == 1 shows that to be true. Because of that, NSC_CloseSession can just call `sftk_DestroySession` directly and leave `sftk_FreeSession` as a no-op to be removed in the future.
* Merge pull request #1262 from athenian200/solaris-workMoonchild2019-11-02-193/+200
|\ | | | | Support Modern Solaris
| * MoonchildProductions#1251 - Part 16: Resolve namespace conflicts with dbm on ↵athenian2002019-10-21-193/+200
| | | | | | | | | | | | | | | | | | | | Solaris. https://bugzilla.mozilla.org/show_bug.cgi?id=1513913 Mozilla's solution to this is arguably overkill, since the namespace issue on Solaris only required them to change (or temporarily undefine) __log2. Instead they changed ALL the functions to be something along the lines of dbm_log2. They haven't changed the external interface at all, though. If you're unhappy with this patch, I think I could also use XP_SOLARIS ifdefs to undefine __log2 prior to where it's declared in the dbm headers. The good thing about Mozilla's solution is that it guarantees this namespace issue never occurs again on any platform, though.
* | Update NSS versionwolfbeast2019-10-24-6/+6
| |
* | Add length checks for cryptographic primitivesKevin Jacobs2019-10-24-9/+56
| | | | | | | | | | This rollup patch adds additional length checks around cryptographic primitives.
* | Support longer (up to RFC maximum) HKDF outputswolfbeast2019-10-24-8/+25
|/ | | | | | HKDF-Expand enforces a maximum output length much shorter than stated in the RFC. This patch aligns the implementation with the RFC by allocating more output space when necessary.
* Update NSS version.wolfbeast2019-07-17-6/+6
|
* Prohibit the use of RSASSA-PKCS1-v1_5 algorithms in TLS 1.3wolfbeast2019-07-17-0/+20
| | | | This is a spec compliance issue.
* Don't unnecessarily strip leading 0's from key material during PKCS11 import.wolfbeast2019-07-17-18/+30
|
* Apply better input checking discipline.wolfbeast2019-07-17-7/+22
|
* Change softoken password rounds to a more conservative number stillwolfbeast2019-07-03-2/+2
| | | | | within industry standard security, considering our db hashing is more CPU intensive than anticipated.
* Update NSS to 3.41.1 (custom)wolfbeast2019-06-27-49/+217
| | | | This resolves #82
* Revert "Update NSS to 3.41.1 (custom)"wolfbeast2019-06-26-213/+45
| | | | This reverts commit fbc2eaacd679f0c484993ffe23d786fd06da22c3.
* Update NSS to 3.41.1 (custom)wolfbeast2019-06-26-45/+213
| | | | This resolves #82
* Update NSS to 3.41wolfbeast2018-12-15-2272/+15450
|
* Update NSS to 3.38wolfbeast2018-08-14-6189/+2224
| | | | | | | | | | | | | - Added HACL*Poly1305 32-bit (INRIA/Microsoft) - Updated to final TLS 1.3 draft version (28) - Removed TLS 1.3 prerelease draft limit check - Removed NPN code - Enabled dev/urandom-only RNG on Linux with NSS_SEED_ONLY_DEV_URANDOM for non-standard environments - Fixed several bugs with TLS 1.3 negotiation - Updated internal certificate store - Added support for the TLS Record Size Limit Extension. - Fixed CVE-2018-0495 - Various security fixes in the ASN.1 code.
* Don't leak newTemplate in pk11_copyAttributes()wolfbeast2018-07-01-2/+3
| | | | Cherry-pick of NSS fix from 3.37
* Update NSS to 3.36.4-RTMJustOff2018-06-11-998/+2625
|
* Revert "Restore NSS default storage file format to DBM when no prefix is given."wolfbeast2018-06-06-5/+1
| | | | This reverts commit b2c78bbf83f75bf034028814329fdd43b6bfe885.
* Restore NSS default storage file format to DBM when no prefix is given.NSS_3.35_TESTwolfbeast2018-06-05-1/+5
|
* Update NSS to 3.35-RTMwolfbeast2018-06-05-13588/+17226
|
* Partially revert 1ef526f0f - sftkpwd.cMatt A. Tobin2018-04-26-2/+2
| | | | #82 #265
* Revert "Update NSS to 3.35-RTM"wolfbeast2018-04-25-17226/+13588
| | | | This reverts commit f1a0f0a56fdd0fc39f255174ce08c06b91c66c94.
* Strengthen the use of the Master Password.wolfbeast2018-04-18-2/+2
| | | | | | | | - Use 30k iterations instead of 1. - Enforce minimum password length of 8 characters. - Adjust strength meter accordingly. This resolves #82.
* Update NSS to 3.35-RTMwolfbeast2018-02-23-13588/+17226
|
* Update NSS to 3.32.1-RTMwolfbeast2018-02-06-13090/+7652
|
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+762712
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-21 09:31:34 +0000