diff options
| author | Nalin Dahyabhai <nalin@dahyabhai.net> | 2013-04-24 14:43:59 -0400 |
|---|---|---|
| committer | Greg Hudson <ghudson@mit.edu> | 2013-05-13 01:59:11 -0400 |
| commit | fad79a9dec35e9839421e8031741a53a714d13c6 (patch) | |
| tree | 3458d019f20cc5d15b26ea09a6734aed1e65879f /src/plugins/locate/python | |
| parent | 333d3acefc8ca386fa006dd7aa5fdacb48d5b088 (diff) | |
| download | krb5-fad79a9dec35e9839421e8031741a53a714d13c6.tar.gz krb5-fad79a9dec35e9839421e8031741a53a714d13c6.tar.xz krb5-fad79a9dec35e9839421e8031741a53a714d13c6.zip | |
In PKINIT NSS crypto code, load certificates first
When using NSS's CMS API to generate signed-data messages, we identify
the key that we want to use for signing by specifying a certificate.
The library then looks up the corresponding private key when it needs to
generate the signature. This lookup fails if a certificate and a its
corresponding private key were loaded key-first, but succeeds if they
were loaded certificate-first (RHBZ#859535). To work around this,
switch to loading the certificate first. (We switch to using different
_pkinit_identity_crypto_file pointers for each instead of reusing just
one, so the diff is messier than it might have been.)
Diffstat (limited to 'src/plugins/locate/python')
0 files changed, 0 insertions, 0 deletions