Entries created as duplicates using references to another entry should also...
A lightweight and easy-to-use password manager
Brought to you by:
dreichl
Menu
▾
▴
#2935 Entries created as duplicates using references to another entry should also reference to its expire date
open
nobody
5
2025-06-28
2025-06-28
No
Current scenario:
one original entry = set with actual login / password - expire date is set
many duplicate + reference entries = set with refs to the original entry's login / password - expire date not set
The duplicate/ref entries can still access the login / password information from the original entry even if the original entry is expired.
The possibility currently available (of having to manually set the expire date in the duplicate/ref entries) seems not good enough: it could be a lot of work to match each of the original entries with its duplicates to have all of them manually set up to the same date every time the original entry's password is updated.
Also, I don't see a scenario where the duplicate/ref entries expire dates would have to have a different value from the original entry, so it looks like it makes sense to automate this, However, if this is a valid scenario, it could be linked to an option at the entry level (if enabled, it will get the expire date from a referenced entry).
Thanks
Link to my comment with the real life situation and impact:
https://sourceforge.net/p/keepass/discussion/329220/thread/a3b22f6b7e/#3b67