-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
FR: optional relative expiration #826
Comments
I had seen #755, and discounted it since it was talking about auto-expiring based on account type (google, etc); I see it is related. Since those kinds of requirements are per-provider and can easily change, I suggest hard-coding those providers into strongbox is not where that kind of thing needs to be maintained. The user should be self-aware of those restrictions and self-impose. I had also seen #194, but "recurring" is different than my use-case, which is simplifying how far into the future one wants the entry to expire. While one might argue "recurring every 6-months", though I think the two efforts combined could look more like:
(Does "recurring" mean to update the expiration the password is changed, or just cycle it based on when recurrence was activated? That's not my use-case, though others may find it useful.) Sorry, I guess I should have highlighted in the original post why this request is distinct from others. I hope it's clear enough how this is different and what value it can hold (to some, at least). Here's what "keepassxc" (linux) offers ("Presets" is a pull-down menu): Thanks! |
I see, thanks for the extra detail, sounds straightforward enough |
Some accounts have expiration/reset criteria on the order of "n-months" or similar. It would be great to be able to set/change an entry's expiration date as a relative option, perhaps a pull-down with 1-week, 2-weeks, 1-month, 2-months, 3-months, 6-months, 1 year. Once selected, this just calculates/sets the (unchanged) expiration field.
(I thought I had asked for this FR already but I cannot find it, my apologies if this is a dupe.)
The text was updated successfully, but these errors were encountered: