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

Enhancement and harmonization of dates in the apps #6985

Open
richsalz opened this issue Aug 16, 2018 · 1 comment
Open

Enhancement and harmonization of dates in the apps #6985

richsalz opened this issue Aug 16, 2018 · 1 comment
Labels
branch: master Merge to master branch triaged: feature The issue/pr requests/adds a feature
Milestone

Comments

@richsalz
Copy link
Contributor

From some old email...

Objects that need dates (x509 etc) will have a standard –start flag.
It takes an ISO date-time, the time defaulting to 00:00. A time and
duration can be specified by putting /duration after the start date.
Or the abosolute time can be specified with an –end flag. For example

-start 2017-02-10/p30d
-start 2017-02-10 –end 2017-03-12

Both mean the same thing, from Feb 10 for 30 days.

It is important not to break the existing flags.

Another option to consider is "-asof" to allow future and past signature checking, for example.

Also, times in the app should not use time_t but instead the ASN1 time type.

@tmshort
Copy link
Contributor

tmshort commented Aug 17, 2018

Note: PR #205

@mattcaswell mattcaswell added this to the Post 1.1.1 milestone Aug 20, 2018
@t8m t8m modified the milestones: Post 1.1.1, Post 3.0.0 Apr 27, 2021
@t8m t8m added branch: master Merge to master branch triaged: feature The issue/pr requests/adds a feature labels Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch: master Merge to master branch triaged: feature The issue/pr requests/adds a feature
Projects
None yet
Development

No branches or pull requests

4 participants