diff options
| author | Carl Hetherington <cth@carlh.net> | 2019-12-01 23:13:25 +0100 |
|---|---|---|
| committer | Carl Hetherington <cth@carlh.net> | 2019-12-01 23:13:25 +0100 |
| commit | 9a5809be580c1a12864d751a710f6783363d3de7 (patch) | |
| tree | 2039fc251ed6bb5abcfe2fd6daa2fe572fac144e /src/exceptions.cc | |
| parent | c78523806e89e4c43015816fcd20db2549992464 (diff) | |
Check that KDM validity periods are safely within the validity periods
of the signing certificate chain.
This does cause problems when you try to create a KDM for a certificate
you just made (due to the fact that certificates always have a start-valid
time of "now") but hopefully this can be fixed up in another commit.
Diffstat (limited to 'src/exceptions.cc')
| -rw-r--r-- | src/exceptions.cc | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/src/exceptions.cc b/src/exceptions.cc index 0b8978dc..19422090 100644 --- a/src/exceptions.cc +++ b/src/exceptions.cc @@ -138,3 +138,14 @@ EmptyAssetPathError::EmptyAssetPathError (string id) { } + +BadKDMDateError::BadKDMDateError (bool starts_too_early) + : runtime_error ( + starts_too_early ? + "KDM validity period starts before or close to the start of the signing certificate validity period" : + "KDM validity ends after or close to the end of the signing certificate's validity period" + ) + , _starts_too_early (starts_too_early) +{ + +} |
