So I thought a little pepper might clue you in about how aggravating this feature is for the people it sounds like you have always kept the URL information (in Firefox) separate from the password information (in KeePass), necessitating a manual inspection of both locations each time you log in I just gave up my firefox integration based on the claims and recommendations about this program, and I either have to kill the rest of my day to make passwords convenient again, or switch back to FF or keepasshttps. It's not like site names and URLs are going to flood the scroll able box on each search. Christ, just remove the restriction entirely. Give us a precise regex pattern to search for a specific word in a specific field. allow or name: modifiers like in database queries, since there'd only be one at once. The circular process of filling in information so I can return to a program that had had the information right there in the first place is absolutely ludicrous, and I'm not going to spend an entire day doing it.įurthermore, unless everyone is on hiatus, I see no reason it still hasn't been addressed after.10 months? For the search, give us anything. I've skimmed through all the issues, and if nothing is catastrophically broken, this should be your one priority until it is finished.
#KYPASS 3 ENTRY LINED OUT UPDATE#
So, this feature assumes that everyone will already have the very optional information they need to update a site,which is a huge mistake in terms of accuracy and in making a critical feature so excessively, singularly narrow and dependent on a database that is already complete and accurate. To Get the program to update an entry after logging in, which is needed to fill in the string fields and establish basic functionality, I have to manually find the login URL domain, manually find the entry I want to change in KeePass, enter the URL, return to the browser and login, then elect to update the entry.
I always just used FF fmanager and KeePass for reference, so I don't have the URL filled out on any of my hundreds of site entries. But easing the assignment of URLs to pre-existing KeePass entries is certainly a valid thing to try to do with the feature so it's definitely worth thinking if we can enable that use-case too. I imagined the update password feature would be most used by people updating passwords that they had already saved (or at least used) through KeeFox so the lack of entries without URLs shouldn't be a problem for that (majority?) use-case. It's been a low priority until recently but with the new update functionality we definitely have another good reason to investigate the impact of that change. Yeah that isn't how it works at the moment but I've been contemplating a change so that KeePassRPC returns all entries and we just filter out the ones without URLs in KeeFox at the points where URLs are required (primarily the list of logins and main panel search results). Ideally, you should be able to search all entries in the database so that you can update any existing replies: This is a spin off of some discussion in says (with regard to the new feature of updating existing entries):
0 kommentar(er)
