Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow timestamping to be per signature configuration. #12

Closed
priteshbandi opened this issue Oct 1, 2021 · 0 comments · Fixed by #15
Closed

Allow timestamping to be per signature configuration. #12

priteshbandi opened this issue Oct 1, 2021 · 0 comments · Fixed by #15
Milestone

Comments

@priteshbandi
Copy link
Contributor

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
  • notation sign <-- only signs

Originally posted by @priteshbandi in #11 (comment)

@priteshbandi priteshbandi changed the title Allow timestamping to be per signing operation configuration. Allow timestamping to be per signature operation configuration. Oct 1, 2021
@priteshbandi priteshbandi changed the title Allow timestamping to be per signature operation configuration. Allow timestamping to be per signature configuration. Oct 1, 2021
@iamsamirzon iamsamirzon added this to the alpha-2 milestone Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants