Closed markcs closed 4 years ago
Thx for the reply, I'll try to solve this rapidly.
It's now fixed in the new version 2.5.0.0beta8.
The latest version on F-Droid still has this issue.
Confirm this, I am on the latest version and the issue is NOT resolved. Why it is closed?
I coded a fix and retested, maybe there was a regression.
I just tested:: Username Magikeyboard Ref -> OK Password Magikeyboard Ref -> OK Username Clipboard Notification Ref Copy -> OK Password Clipboard Notification Ref Copy -> OK Username Clipboard Button Ref Copy -> KO Password Clipboard Button Ref Copy -> KO Username Autofill Ref -> OK Password Autofill Ref -> OK
I fixed the problem in development, I added the references for custom fields.
It does not work for the magic keyboard! I have entries with a custom attribute named "E-Mail". My username references it as "{S:E-Mail}", but the reference is not resolved by the keyboard!
It does not work for me either. I have a password referenced via UUID as {REF:P@I:xxxxxxxxxxxxxxxxxxx} and this is what is pasted through magickeyboard instead of the actual password.
It doesn't work with ref S because it is not implemented but should work with P and I. @fritut08 Are you using the latest version of the application?
Yes, it is the newest version
Can you upload a test database that I can debug?
I think I know, what the problem is. I created kind of a reference cascade 😄
When I try to paste the password of entry 3 the UUID of entry 1 is pasted. So it does correctly dereference the first link but fails to check whether that entry also contains a reference. Keepass on desktop manages to find the correct password. Do you think you will be able to implement this or is this cascading too exotic? 😄
This should be feasible but it can cause significant performance problems during searches because at each iteration, the field used as a reference (not necessarily a UUID) should be searched and this can be time consuming with a large database. I thought from memory that I had handled this case by having set a loop stop to avoid making infinite references but I may have broken the concept when I optimized the search. Can you open a new issue for this respecting the issue template (with a test database it would be great)?
Yes, I will try. Thanks.
Edit: Done! https://github.com/Kunzisoft/KeePassDX/issues/1027
Keepass allows field references in usernames and passwords. From https://keepass.info/help/base/fieldrefs.html
KeePassDX copies the reference text and NOT the actual reference value.