diff options
| author | Daiki Ueno <dueno@redhat.com> | 2020-01-10 20:34:53 +0100 |
|---|---|---|
| committer | wolfbeast <mcwerewolf@wolfbeast.com> | 2020-01-10 20:34:53 +0100 |
| commit | f64e760ab09eb9cdc110fd3f24d77aed6918e1fa (patch) | |
| tree | 1ea664647a2702cb362d7f0ce93fb0364cbdea4e /chrome | |
| parent | 095a02f2597992e791d304270335d94c3120f2b6 (diff) | |
| download | UXP-f64e760ab09eb9cdc110fd3f24d77aed6918e1fa.tar UXP-f64e760ab09eb9cdc110fd3f24d77aed6918e1fa.tar.gz UXP-f64e760ab09eb9cdc110fd3f24d77aed6918e1fa.tar.lz UXP-f64e760ab09eb9cdc110fd3f24d77aed6918e1fa.tar.xz UXP-f64e760ab09eb9cdc110fd3f24d77aed6918e1fa.zip | |
Issue #1338 - Followup: certdb: propagate trust information if trust
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.
Diffstat (limited to 'chrome')
0 files changed, 0 insertions, 0 deletions