Browser
extensions
Download and install the QubKey browser extension for Chrome or Firefox. You must configure Native Messaging with the desktop app before use.
Download packages
Release 1.0.0 — file names match the packages from the extension release folder.
Chrome: The .zip is only an archive. Extract it to a folder with manifest.json at the root, then in chrome://extensions enable Developer mode and use “Load unpacked”. Chrome does not install the zip by double-clicking it.
Firefox: The .xpi is for AMO submission or specific local installs. Standard Firefox Release usually requires a Mozilla-signed build from addons.mozilla.org.
Prerequisites
The extension talks to the QubKey desktop app through Native Messaging. Set up the native host (JSON manifest, binary, paths) using the Native Messaging documentation in your desktop project before use.
After loading the extension manually, copy the extension ID shown in the browser into the com.passmanager.native.json host manifest as described in that documentation.
Google Chrome and Chromium-based browsers
Browsers such as Microsoft Edge can use the same steps: extract the archive and load the unpacked folder from the extensions page with Developer mode enabled.
Test install (developer mode)
- Download and unzip passmanager-chrome-1.0.0.zip into a fixed folder (for example PassManager-Chrome-1.0.0/) with manifest.json at the root.
- Open chrome://extensions/.
- Turn on Developer mode (top right).
- Click “Load unpacked” and choose the extracted folder.
- Note the extension ID for your Native Messaging configuration.
Mozilla Firefox
Signed extension (recommended)
After publishing on addons.mozilla.org (AMO), users install the add-on in one click like any standard extension, without about:debugging. The .xpi is the package to upload to AMO (or a build artifact) once API access is configured.
Local .xpi (development / beta)
On Firefox Nightly or Developer Edition, or if signature verification is turned off (not recommended in production), you may install from about:addons → gear menu → Install Add-on From File and pick the .xpi. On standard Firefox Release, an unsigned .xpi is usually blocked—use an AMO-signed build for normal distribution.
Temporary unpacked load (advanced tests)
Developers can load the firefox/ source folder via about:debugging → This Firefox → Load Temporary Add-on pointing at firefox/manifest.json. This is a development workflow, not an end-user installer.
Summary
| Target | Typical use (no dev mode) | Local / team testing |
|---|---|---|
| Chrome | — | Unzip → chrome://extensions → Load unpacked |
| Firefox | Signed .xpi via AMO | Local .xpi rules, or about:debugging + source folder |