Keeautoexec12/20/2023 My suggestion is to define a device/app-ID (e.g. Except for WebDav/FTP entries, there are no paths which are supported in KeePass as well as KP2A. many entries store absolute paths or paths relative to the Keepass executable. I don't think that a single AutoOpen entry as it is defined at present will work across devices, e.g. I am interested in feedback, both from KeePass users and Dominik, about the following thoughts: I suppose that many users would benefit from having something like KeeAutoExec on Android as well, so I am planning to integrate this in KP2A, too. Otherwise I am expecting people to complain if they add child databases in Keepass2Android which have the IfDevice field set because they should be restricted to the Android device.As the author of Keepass2Android, I have recently added support for having several databases open simultaneously (). If an AutoOpen entry has a field "IfDevice", this field should be respected. Would be great if KeepassXC would support the IfDevice extension. The feature is implemented in Keepass2Android's current beta ( ) which will soon be released to stable. This makes sense for local files and also provides good support for mobile apps where paths e.g. The main update is introducing support for an IfDevice field which allows to select which entries should be opened on which devices. KeeAutoExec functionality has been added ( #477), but KeeAutoExec has sinced received an update which I have requested and discussed with Dominic in. I suggest that the KeepassXC implementation is updated also to keep best compatibility. KeeAutoExec functionality has been updated for Keepass2 and Keepass2Android.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |