Class CryptoConstraintsFailure
java.lang.Object
java.lang.Throwable
java.lang.Exception
br.ufsc.labsec.validationResult.results.reasons.ValidationResultReason
br.ufsc.labsec.validationResult.exceptions.invalidExceptions.ReasonForTotalFailed
br.ufsc.labsec.validationResult.exceptions.invalidExceptions.CryptoConstraintsFailure
- All Implemented Interfaces:
ConstraintsFailure, Serializable
The signature is considered invalid because at least one of the algorithms that have been used
in a material (e.g. the signature value, a certificate...) involved in validating the signature
or the size of the keys used with such an algorithm is no longer considered reliable and the
Signature Validation Algorithm can ascertain that this material was produced after the time up
to which this algorithm was considered secure.
The process shall output: TODO
- a list of algorithms, together with the size of the key, if applicable, that have been used in validation of the signature but no longer are considered reliable together with a time up to which each of the listed algorithms were considered secure.
- The list of material where each of the listed algorithms were used.
- See Also:
-
Constructor Summary
Constructors -
Method Summary
Methods inherited from class ValidationResultReason
assertReason, getReason, is, isIn, isReasonForIndeterminate, isReasonForTotalFailed, isRevokedReason, isValidationNotPossible, result, setValidationNotPossibleMethods inherited from class Throwable
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
-
Constructor Details
-
CryptoConstraintsFailure
-
-
Method Details
-
getDetails
- Specified by:
getDetailsin interfaceConstraintsFailure
-