tree 29af2d33c718dfeb54c01ee664f0ca0288d2690e
parent 9c6118c498c13be6a2fadd7f79ec2b577fb5450f
author Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com> 1498733727 +0200
committer Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com> 1502183210 +0200

Add badtime-skipping feature to new function

This is from the morally 5th (and soon obsolete) invocation of this function
in verify_top().

Doing this badtime-skipping when we search for a parent in the provided chain
is a change of behaviour, but it's backwards-compatible: it can only cause us
to accept valid chains that we used to reject before. Eg if the peer has a
chain with two version of an intermediate certificate with different validity
periods, the first non valid and the second valid - such cases are probably
rare or users would have complained already, but it doesn't hurt to handle it
properly as it allows for more uniform code.