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
One signer implementation(like file-based one) can be reused by multiple organization. Some organizations might not want to timestamp signature because of availability concerns or something else but other might prefer to timestamp signature.
So there should be a way to for user to disable/enable time-stamping on per signature basis. One way to achieve is that only add timestamp when user explicitly specifies it
notation sign --timestamp=${serverURL} <-- signs and timestamps
The text was updated successfully, but these errors were encountered:
priteshbandi
changed the title
Allow timestamping to be per signing operation configuration.
Allow timestamping to be per signature operation configuration.
Oct 1, 2021
priteshbandi
changed the title
Allow timestamping to be per signature operation configuration.
Allow timestamping to be per signature configuration.
Oct 1, 2021
One signer implementation(like file-based one) can be reused by multiple organization. Some organizations might not want to timestamp signature because of availability concerns or something else but other might prefer to timestamp signature.
So there should be a way to for user to disable/enable time-stamping on per signature basis. One way to achieve is that only add timestamp when user explicitly specifies it
Originally posted by @priteshbandi in #11 (comment)
The text was updated successfully, but these errors were encountered: