Interface TraceableSignatureVerificationData
- All Superinterfaces:
SignatureVerificationData<TraceableSignatureVerificationData>
FreeTransactionManager.prepareVerifySignature(SignatureVerificationData)
method for traceable
signature verification using the "PSO Verify Signature" command.
An instance of this interface can be obtained via the method LegacySamApiFactory.createTraceableSignatureVerificationData()
.
- Since:
- 0.1.0
-
Method Summary
Modifier and TypeMethodDescriptionIndicates that the signature has been computed in non "Busy" mode.withSamTraceabilityMode
(int offset, SamTraceabilityMode samTraceabilityMode, LegacySamRevocationServiceSpi samRevocationService) Indicates that the signature has been computed in "SAM traceability" mode and therefore whether the revocation status of the signing SAM should be checked or not.Methods inherited from interface org.eclipse.keypop.calypso.crypto.legacysam.transaction.SignatureVerificationData
isSignatureValid, setData, setKeyDiversifier
-
Method Details
-
withSamTraceabilityMode
TraceableSignatureVerificationData withSamTraceabilityMode(int offset, SamTraceabilityMode samTraceabilityMode, LegacySamRevocationServiceSpi samRevocationService) Indicates that the signature has been computed in "SAM traceability" mode and therefore whether the revocation status of the signing SAM should be checked or not.By default, the signature is not supposed to have been computed in "SAM traceability" mode.
- Parameters:
offset
- The offset in bits of the SAM traceability data.samTraceabilityMode
- The SAM traceability mode which have been used.samRevocationService
- If it is provided, then the revocation status of the SAM that signed the data will be checked by the SAM revocation service.- Returns:
- The current instance.
- Throws:
IllegalArgumentException
- If the provided samTraceabilityMode is null.- Since:
- 0.1.0
- See Also:
-
withoutBusyMode
TraceableSignatureVerificationData withoutBusyMode()Indicates that the signature has been computed in non "Busy" mode.By default, the signature is supposed to have been computed in "Busy" mode.
The signature may have been generated with "Busy mode" enabled. In this mode, after a "PSO Verify Signature" failing because of an incorrect signature, during a few seconds the SAM rejects any "PSO Verify Signature" commands with "Busy" mode by responding with the "busy" status word.
When a "PSO Verify Signature" fails with the busy status, the terminal should repeat the command until the SAM is not busy anymore.
The busy mode duration is typically of a few seconds, and it is never of greater than ten seconds.
Note that after a reset of the SAM, "PSO Verify Signature" commands being in "Busy" mode fail with the busy status until the end of the busy mode duration.
- Returns:
- The current instance.
- Since:
- 0.1.0
- See Also:
-