summaryrefslogtreecommitdiffstats
path: root/third_party/aom/tools/gen_constrained_tokenset.py
diff options
context:
space:
mode:
authorDaiki Ueno <dueno@redhat.com>2020-01-10 20:34:53 +0100
committerwolfbeast <mcwerewolf@wolfbeast.com>2020-01-10 20:34:53 +0100
commitf64e760ab09eb9cdc110fd3f24d77aed6918e1fa (patch)
tree1ea664647a2702cb362d7f0ce93fb0364cbdea4e /third_party/aom/tools/gen_constrained_tokenset.py
parent095a02f2597992e791d304270335d94c3120f2b6 (diff)
downloadUXP-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 'third_party/aom/tools/gen_constrained_tokenset.py')
0 files changed, 0 insertions, 0 deletions