Closed
Bug 1585189
Opened 5 years ago
Closed 4 years ago
NSS database uses 3DES instead of AES to encrypt DB entries
Categories
(NSS :: Libraries, enhancement, P2)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rrelyea, Assigned: marcus.apb)
Details
Attachments
(1 file, 1 obsolete file)
The current NSS database can use multiple different algorithms to encrypt keys with. Currently it uses 3DES, which we are moving away from. It should use AES.
This is sort of related to the interation count bug 1562671 and bug 524403.
bob
|
||
Updated•5 years ago
|
Assignee: nobody → marcus.apb
Status: NEW → ASSIGNED
Priority: -- → P2
|
Assignee | |
Comment 1•5 years ago
|
||
|
Reporter | |
Comment 2•5 years ago
|
||
Our NSS DB uses 3DES internally to encrypt their entries.
This patch changes the default algorithm for AES256 to increase the security.
This patch also adds code to use AES Wrap in the future. It also adds an integrity
check to the AES256 CBC. The change only affects sqlite databases.
bob
|
|
Reporter | |
Updated•4 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
|
||
Comment 3•4 years ago
|
||
|
||
Updated•4 years ago
|
Attachment #9101912 -
Attachment is obsolete: true
|
||
Comment 4•4 years ago
|
||
which NSS version did it land in?
|
|
Reporter | |
Comment 5•4 years ago
|
||
NSS 3.49
You need to log in
before you can comment on or make changes to this bug.
Description
•