Because of the nature of keepass dbx files as a format which you then read rather than interface with a long running process, one would need to reenter the db password every execution - which is going to quickly get VERY annoying.
Or I'd need to background a sub-process that would do the heavy lifting and then somehow authenticate between the parent and child process to then retrieve the db pass, or result - which smells.
Ideally, some kind of common cache/cookie type API would exist (my google foo can't find) that I could store and retrieve the result in a secure way with knowledge that some OS component would self destruct it after time.
Because of the nature of keepass dbx files as a format which you then read rather than interface with a long running process, one would need to reenter the db password every execution - which is going to quickly get VERY annoying.
Or I'd need to background a sub-process that would do the heavy lifting and then somehow authenticate between the parent and child process to then retrieve the db pass, or result - which smells.
Ideally, some kind of common cache/cookie type API would exist (my google foo can't find) that I could store and retrieve the result in a secure way with knowledge that some OS component would self destruct it after time.
Marking as blocked waiting for better ideas.