f1262147a3
* Save last 5 passwords. * Move password history to seperate page. * Use the util helpers for accessing the local storage. * Change close to back for password history. Remove unused html. * Change orderBy to use the date instead of magic array. * Move historyService to background. * Add passwords generated from shortcut and contextmenu to history. * Fix return to edit/add not working in password generator history. * Change password icon to clipboard. * Change link to password history to use on-click. * Clear password generator history on logout. * Code style fix. * Add new .wrap class for wrapping long text. Fix password icon. |
||
---|---|---|
src | ||
store | ||
.gitignore | ||
bitwarden-browser.sln | ||
CONTRIBUTING.md | ||
crowdin.yml | ||
gulpfile.js | ||
LICENSE.txt | ||
package.json | ||
README.md | ||
SECURITY.md | ||
webfonts.list |
bitwarden Browser Extension
The bitwarden browser extension is written using the Chrome Web Extension API and AngularJS.
Build/Run
Requirements
By default the extension is targeting the production API. If you are running the Core API locally,
you'll need to switch the extension to target your local API. Open src/services/apiService.js
and set this.baseUrl
to your local
API instance (ex. http://localhost:4000
).
Then run the following commands:
npm install
gulp build
You can now load the extension into your browser through the browser's extension tools page:
- Chrome/Opera:
- Type
chrome://extensions
in your address bar to bring up the extensions page. - Enable developer mode (checkbox)
- Click the "Load unpacked extension" button, navigate to the
src
folder of your local extension instance, and click "Ok".
- Type
- Firefox
- Type
about:debugging
in your address bar to bring up the add-ons page. - Click the
Load Temporary Add-on
button, navigate to thesrc/manifest.json
file, and "Open".
- Type
Contribute
Code contributions are welcome! Please commit any pull requests against the master
branch. Learn more about how to contribute
by reading the CONTRIBUTING.md
file.
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md
file.