Similar questions are often asked so I was part way through
writing a new page in the manual to help explain how to work with
existing passwords. Unfortunately, Sourceforge have just announced that
they will be deleting the KeeFox manual in a couple of months time so it
doesn't seem worthwhile me maintaining it in its current location. I've
pasted the text of the new page below and will soon put it into
whatever manual I find to replace the current one.
Please let me know if this helps or if there are further points that require clarification.
------- Working with existing passwords
are a variety of ways to get KeeFox to work with existing passwords.
The best approach is up to you but depending on how many you have and
where they are stored, there are some approaches that I would recommend
over others. This section of the manual will help you to understand
1) Do nothing
Good when: You're pushed for time and most of your logins are for simple forms containing only a username and password field
This approach works because KeeFox always tries to fallback to the
existing KeePass username and password. KeeFox has to guess which form
fields are for the username and password - simple forms with just one
text box and one password box are easy to get right but once forms
contain multiple text or password boxes or other types of form field it
gets more and more likely that KeeFox will get it wrong and that's when
the options below are worth considering.
You might want to consider using the "never for this site" button in
order to stop KeeFox asking you to save the login each time you login
but of course this might backfire in the future if you actually want to
save a new login somewhere on that site. If you have a few seconds to
spare, option 2 below might be better.
2) Allow KeeFox to save the login as a new entry in KeePass and then delete the old entry
Good when: Doing nothing is proving either annoying or inaccurate and your login entries in KeePass are simple to re-create
is the easiest way to give KeeFox a helping hand to identify the
correct login forms and correct fields within those forms. Obviously you
should be careful before deciding to delete your old entries - consider
whether any file attachments or history of entry changes are important
before taking this approach.
3) Allow KeeFox to save the login as a new entry in KeePass, modify the old entry and then delete the one KeeFox created
Good when: Doing nothing is proving either annoying or inaccurate and
your existing entry contains extra information that you would like to
This is the most time consuming approach but does give you complete
control over the final KeePass entry. You would typically want to use
this when your KeePass entry already contains other information beyond
simply a username and password.
The idea is to get an entry into your database that contains all of the
information that KeeFox would save if you were creating the entry from
KeeFox to start with. You can then refer to the information shown in the
KeeFox tab for the new entry in order to reproduce the relevant KeeFox
data in your old entry. The key sections to look for are the URL and the
NB: The first text field is always the "username" and the first password
is always the "password" - this will usually be the first text field or
password on the visible web page but that's not guaranteed.
Finally, unless you are re-creating all of your entries via KeeFox
you'll probably have at least some entries that do not have a website
icon (favicon). You might find it easier to differentiate between logins
if you use the KeePass Favicon Downloader plugin to get those icons.
You might also want to use that plugin from time to time to update the
entries that KeeFox creates because KeeFox won't update the icons once
its first created the entry and websites do change their icons
Leave a comment on luckyrat's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic