L'estensione per Browser di Bitwarden funziona con Chrome, Firefox, Edge, Opera, Safari, Vivaldi, brave, Tor Browser. L'istanza bitwarden dei devol comprende tutte le funzioni premium di bitwarden https://vaultwarden.devol.it
Go to file
Snyk bot 767fa7beac
fix: upgrade @microsoft/signalr from 3.1.0 to 3.1.13 (#823)
Snyk has created this PR to upgrade @microsoft/signalr from 3.1.0 to 3.1.13.

See this package in npm:
https://www.npmjs.com/package/@microsoft/signalr

See this project in Snyk:
https://app.snyk.io/org/kspearrin/project/257fd10d-8b4a-4ead-b08e-11ddee875925?utm_source=github&utm_medium=upgrade-pr
2021-04-12 10:56:04 -04:00
.github Merge pull request #704 from joseph-flinn/master 2021-03-15 14:40:03 -07:00
.vscode persist and restore window state 2018-02-14 15:34:17 -05:00
jslib@85893f5f9e bump jslib 2021-04-09 15:41:33 +10:00
patches Temporary fix for building masdev (#809) 2021-03-24 17:17:03 +01:00
resources Adjust smaller macOS icons padding 2021-04-01 00:49:01 +02:00
scripts Add script for downloading legacy safari extension (#796) 2021-03-19 17:18:48 +01:00
src Merge branch 'master' into verify-email-for-send 2021-04-09 15:41:49 +10:00
stores Updated year to current in copyright(s) 2021-02-24 22:52:53 +01:00
.editorconfig update settings 2018-04-10 22:05:28 -04:00
.gitignore Add script for downloading legacy safari extension (#796) 2021-03-19 17:18:48 +01:00
.gitmodules submodule via https 2018-02-19 16:26:53 -05:00
.nvmrc add .nvmrc to use node 10 (#164) 2019-11-16 22:46:47 -05:00
CONTRIBUTING.md fix typo 2020-11-10 17:44:04 +10:00
ISSUE_TEMPLATE.md Change Windows store -> Microsoft store 2021-03-17 18:23:00 +01:00
LICENSE.txt license and contrib 2018-01-26 16:07:42 -05:00
README.md Removed travis.yml including the badge in README.md 2021-03-25 19:40:51 +01:00
SECURITY.md uppercase Bitwarden 2018-02-27 13:41:47 -05:00
crowdin.yml map en-IN 2020-09-28 14:21:04 -04:00
gulpfile.js sweetalert: move to sweetalert2. (#388) 2020-02-24 09:45:01 -05:00
package-lock.json fix: upgrade @microsoft/signalr from 3.1.0 to 3.1.13 (#823) 2021-04-12 10:56:04 -04:00
package.json fix: upgrade @microsoft/signalr from 3.1.0 to 3.1.13 (#823) 2021-04-12 10:56:04 -04:00
sign.js switching signing back to signing all .exe files and adding another job that doesn't sign the files for the Windows Store 2021-01-24 23:23:41 +00:00
tsconfig.json Initial PoC for browser <-> desktop communication 2020-10-05 15:27:52 +02:00
tslint.json Add trailing comma to linter 2021-02-08 12:58:44 -06:00
webfonts.list gulp task for webfonts 2018-08-08 12:47:54 -04:00
webpack.main.js Fix electron error on native messaging 2020-12-29 20:53:29 +01:00
webpack.renderer.js update formatting 2020-05-08 12:11:54 -04:00

README.md

Github Workflow build on master Crowdin Join the chat at https://gitter.im/bitwarden/Lobby

Bitwarden Desktop Application

Platforms

The Bitwarden desktop app is written using Electron and Angular. The application installs on Windows, macOS, and Linux distributions.

Desktop Vault

Build/Run

Requirements

  • Node.js
  • Windows users: To compile the native node modules used in the app you will need the Visual C++ toolset, available through the standard Visual Studio installer. You will also need to install the Microsoft Build Tools 2015 and Windows 10 SDK 17134 as additional dependencies in the Visual Studio installer.

Run the app

npm install
npm run electron

Debug Native Messaging

Native Messaging (communication with the browser extension) works by having the browser start a lightweight proxy application baked into our desktop binary. To setup an environment which allows for easy debugging you will need to build the application for distribution, i.e. npm run dist:<platform>, start the dist version and enable desktop integration. This will write some manifests to disk, Consult the native manifests documentation for more details of the manifest format, and the exact locations for the different platforms. Note that disabling the desktop integration will delete the manifests, and the files will need to be updated again.

The generated manifests are pre-configured with the production ID for the browser extensions. In order to use them with the development builds, the browser extension ID of the development build needs to be added to the allowed_extensions section of the manifest. These IDs are generated by the browser, and can be found in the extension settings within the browser.

It will then be possible to run the desktop application as usual using npm run electron and communicate with the browser.

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.