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.

1 files changed, 13 insertions, 0 deletions

diff --git a/src/exceptions.h b/src/exceptions.h
index 1e9bd2d7..17b18eb2 100644
--- a/src/exceptions.h
+++ b/src/exceptions.h
@@ -234,6 +234,19 @@ public:
 	EmptyAssetPathError (std::string id);
 };
 
+class BadKDMDateError : public std::runtime_error
+{
+public:
+	BadKDMDateError (bool starts_too_early);
+
+	bool starts_too_early () const {
+		return _starts_too_early;
+	}
+
+private:
+	bool _starts_too_early;
+};
+
 }
 
 #endif