replaced chromeIPass and passIFox with KeePassHTTP-connector

project.html

@@ -25,10 +25,10 @@ <h5>Additional Features</h5>
         <li>Using website favicons as entry icons
         <li>Merging of databases
         <li>Automatic reload when the database was changed externally
-        <li>KeePassHTTP support for use with
-            <a href="https://addons.mozilla.org/en-us/firefox/addon/passifox/">PassIFox</a> in Mozilla Firefox,
-            <a href="https://chrome.google.com/webstore/detail/chromeipass/ompiailgknfdndiefoaoiligalphfdae">chromeIPass</a>
-            in Google Chrome and Chromium and <a href="https://github.com/mmichaa/passafari.safariextension/">passafari</a> in Safari.
+        <li>KeePassHTTP support for use with KeePassHTTP-Connector available for 
+            <a href="https://addons.mozilla.org/en-US/firefox/addon/keepasshttp-connector/">Mozilla Firefox</a> and
+            <a href="https://chrome.google.com/webstore/detail/keepasshttp-connector/dafgdjggglmmknipkhngniifhplpcldb">Google Chrome</a>,
+            and <a href="https://github.com/mmichaa/passafari.safariextension/">passafari</a> for Safari.
         <li>Many bug fixes
     </ul>
 
@@ -38,7 +38,7 @@ <h5>Additional Features</h5>
     <div class="info">
         <h6>A note about KeePassHTTP</h6>
         <p>KeePassHTTP is not a highly secure protocol and has certain flaws which allow an attacker to decrypt your
-            passwords if they manage to intercept communication between a KeePassHTTP server and PassIFox/chromeIPass over a
+            passwords if they manage to intercept communication between a KeePassHTTP server and KeePassHTTP-Connector over a
             network connection (see <a href="https://github.com/pfn/keepasshttp/issues/258">here</a> and <a
                     href="https://github.com/keepassxreboot/keepassxc/issues/147">here</a>). KeePassXC therefore strictly
             limits communication between itself and the browser plugin to your local computer. As long as your computer is