I am using KeePass v 2.26, KeePassHttp v 1.8.3.0, chromeIPass v 2.6.7, GoogleSync v 1.6.0 and KPScript v 2.26.00, currently on Win Vista SP2 and Win XP SP3. It will soon be extended to two more Vistas and a Linux. On the Win boxes, I have separate Admin & User accounts, but there is one KeyPass database, shared by the users and synced between computers with GoogleSync.
I had originally planned to give both users equal access to KeePass, but soon discover that KeePassHttp has only one Listening Port and I was unable to share the Key Association Password between Admin and User. So I decided to use chromeIPass and KeePassHttp only in User, and in Admin, where I avoid going online anyhow, I would copy & paste directly from KeePass. However, even if I didn’t use it, I still had an active chromeIPass on Chrome in Admin and all of the symptoms of multiple KeePassHttps continued.
A description of the most obvious symptoms follows: After I opened Chrome, when I would click the chromeIPass button, it would brighten, recognizing that it had been clicked, but nothing would happened. So I would sometimes close & reopen KeePass and close & reopen Chrome; then go through the same routine, with the same outcome. Occasionally, Chrome would crash, but eventually, on restarting, it would have a message, “Chrome didn’t shut down correctly…” And finally, I was rewarded with a little red “X” on the chromeIPass icon and I could enter a new Key Association Password, if necessary.
I checked port 19455 with netstat and “LISTENING” was reported back, but I could not determine how many listeners there were. I then checked port 19450 and found that it was free. My next step, in User & Admin was to go to chromeIPass Settings and change the port to 19450. I then went to KeePassHttp Options in Tools in both User & Admin and changed the port to 19450 and hit “Save”. It was accepted and I was instructed to restart KeePass, which I did. In fact, I restarted the computer. Nevertheless, no matter what I did, when I returned to Options, the port had been changed back to 19455 (or never changed in KeePass.config.xml). My solution in chromeIPass was this: For User, changing the port back to 19455 and leaving Admin at 19450. The result was that the problems seem to have gone away, plus I learned that the settings in chromeIPass are per user.
I am not going to touch a thing for awhile, but I would welcome some advice. What were the design intentions for KeePassHttp concerning how one should handle this? Is there a better way than what I did? From something I read, I got the impression that there might be provision for multiple KeePassHttp.plgx files. Apparently, their name makes no difference. Could I have a second plug-in listen on 19450 for Admin? KeePass.config.xml’s Custom section has ten items for KeePassHttp and the last one specifies the Listening Port. That file exists in Program Files and in User Profiles. How would all of this work if I introduced another KeePassHttp.plgx? In the same vein, the Listening Port appears in KeePassHttp Options. Is this propagated when the database is synced? I would certainly appreciate any input you can provide.
I am using KeePass v 2.26, KeePassHttp v 1.8.3.0, chromeIPass v 2.6.7, GoogleSync v 1.6.0 and KPScript v 2.26.00, currently on Win Vista SP2 and Win XP SP3. It will soon be extended to two more Vistas and a Linux. On the Win boxes, I have separate Admin & User accounts, but there is one KeyPass database, shared by the users and synced between computers with GoogleSync.
I had originally planned to give both users equal access to KeePass, but soon discover that KeePassHttp has only one Listening Port and I was unable to share the Key Association Password between Admin and User. So I decided to use chromeIPass and KeePassHttp only in User, and in Admin, where I avoid going online anyhow, I would copy & paste directly from KeePass. However, even if I didn’t use it, I still had an active chromeIPass on Chrome in Admin and all of the symptoms of multiple KeePassHttps continued.
A description of the most obvious symptoms follows: After I opened Chrome, when I would click the chromeIPass button, it would brighten, recognizing that it had been clicked, but nothing would happened. So I would sometimes close & reopen KeePass and close & reopen Chrome; then go through the same routine, with the same outcome. Occasionally, Chrome would crash, but eventually, on restarting, it would have a message, “Chrome didn’t shut down correctly…” And finally, I was rewarded with a little red “X” on the chromeIPass icon and I could enter a new Key Association Password, if necessary.
I checked port 19455 with netstat and “LISTENING” was reported back, but I could not determine how many listeners there were. I then checked port 19450 and found that it was free. My next step, in User & Admin was to go to chromeIPass Settings and change the port to 19450. I then went to KeePassHttp Options in Tools in both User & Admin and changed the port to 19450 and hit “Save”. It was accepted and I was instructed to restart KeePass, which I did. In fact, I restarted the computer. Nevertheless, no matter what I did, when I returned to Options, the port had been changed back to 19455 (or never changed in KeePass.config.xml). My solution in chromeIPass was this: For User, changing the port back to 19455 and leaving Admin at 19450. The result was that the problems seem to have gone away, plus I learned that the settings in chromeIPass are per user.
I am not going to touch a thing for awhile, but I would welcome some advice. What were the design intentions for KeePassHttp concerning how one should handle this? Is there a better way than what I did? From something I read, I got the impression that there might be provision for multiple KeePassHttp.plgx files. Apparently, their name makes no difference. Could I have a second plug-in listen on 19450 for Admin? KeePass.config.xml’s Custom section has ten items for KeePassHttp and the last one specifies the Listening Port. That file exists in Program Files and in User Profiles. How would all of this work if I introduced another KeePassHttp.plgx? In the same vein, the Listening Port appears in KeePassHttp Options. Is this propagated when the database is synced? I would certainly appreciate any input you can provide.