summaryrefslogtreecommitdiffstats
path: root/security/nss/lib/softoken
Commit message (Collapse)AuthorAgeLines
* [NSS] Version and build bumpMoonchild2020-08-30-2/+2
|
* [NSS] Prevent slotLock race in NSC_GetTokenInfoJ.C. Jones2020-08-30-2/+4
| | | | | Basically, NSC_GetTokenInfo doesn't lock slot->slotLock before accessing slot after obtaining it, even though slotLock is defined as its lock.
* [NSS] Version and build bumpMoonchild2020-07-10-2/+2
|
* [NSS] Bump NSS versionMoonchild2020-06-03-2/+2
|
* 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-1/+1
| | | | | | | 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 - Part 2: Update NSS to 3.48-RTMwolfbeast2020-01-02-433/+2716
|
* Update NSS version.wolfbeast2019-12-06-2/+2
|
* [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.
* Update NSS versionwolfbeast2019-10-24-2/+2
|
* 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-2/+2
|
* Don't unnecessarily strip leading 0's from key material during PKCS11 import.wolfbeast2019-07-17-4/+4
|
* 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-45/+213
| | | | This resolves #82
* Revert "Update NSS to 3.41.1 (custom)"wolfbeast2019-06-26-211/+43
| | | | This reverts commit fbc2eaacd679f0c484993ffe23d786fd06da22c3.
* Update NSS to 3.41.1 (custom)wolfbeast2019-06-26-43/+211
| | | | This resolves #82
* Update NSS to 3.41wolfbeast2018-12-15-3/+3
|
* Update NSS to 3.38wolfbeast2018-08-14-86/+271
| | | | | | | | | | | | | - 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.
* Update NSS to 3.36.4-RTMJustOff2018-06-11-3/+3
|
* Update NSS to 3.35-RTMwolfbeast2018-06-05-194/+461
|
* Partially revert 1ef526f0f - sftkpwd.cMatt A. Tobin2018-04-26-2/+2
| | | | #82 #265
* Revert "Update NSS to 3.35-RTM"wolfbeast2018-04-25-461/+194
| | | | 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-194/+461
|
* Update NSS to 3.32.1-RTMwolfbeast2018-02-06-121/+147
|
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+45572