Bug #4758
closed
ValidatorPolicyConfig segfaults when loading policy without assigning Validator instance
Added by Alex Afanasyev about 6 years ago.
Updated over 3 years ago.
Description
ValidatorPolicyConfig cannot be used by itself and requires Validator instance to be assigned prior loading any policy. At least, the implementation should throw a proper error.
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
FYI. The specific error that triggered segfault of NFD was a result of dereferencing nullptr m_validator in ValidatorPolicyConfig::processConfigTrustAnchor method, i.e., if security section includes real trust anchor(s) (as opposite to have "any" trust anchor). If by some magic it would not have segfaulted there, it would whenever config is being reloaded.
- Status changed from Code review to Closed
- Tags set to ValidatorConfig
Also available in: Atom
PDF
Updated by 
Updated by