You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, no checks are performed, wrt the time difference between the creation of an attestation and an assertion.
This is especially important for the key attestation scenario, since an assertion are created right after an attestation.
As the assertion contains no signature time, the only indication we have, is the time difference between the creation of an attestation and the point in time the assertion is checked.
Is this even sensible here, or should this be handled in whichever business logic integrates this library (i.e. through expiring nonces)?
Possible implementation: Make this check optional through a nullable configuration parameter.
Discussion point:
sane default?
null by default?
no defaults?
The text was updated successfully, but these errors were encountered:
Currently, no checks are performed, wrt the time difference between the creation of an attestation and an assertion.
This is especially important for the key attestation scenario, since an assertion are created right after an attestation.
As the assertion contains no signature time, the only indication we have, is the time difference between the creation of an attestation and the point in time the assertion is checked.
Is this even sensible here, or should this be handled in whichever business logic integrates this library (i.e. through expiring nonces)?
Possible implementation: Make this check optional through a nullable configuration parameter.
Discussion point:
The text was updated successfully, but these errors were encountered: