mirror of
https://github.com/bitwarden/help
synced 2025-12-06 00:03:30 +00:00
Release Updates (#474)
* Send Staging (#447) * - js for in-page tabs - send category early drafts of articles - send images * fix scrolling on tab * send web vault * mobile image * redone 'receive send' article * send from browser ext & mobile * send work * improvements to 'about' * send additions * so much send * lotsa send * all send all the time * ain't nothin but a send thang * cli * send cli * simple cli sends in /create-send/ * simple disable & delete in /send-lifespan/ * send desktop screenshots * send final cleanup * cli final cleanup * send edits * fix * send final touches * fixed links & non-send updates * new import message documentation, several import articles condensed to use tabs, U2F support for Edge, excluded domains article, remove in innacurate note on emergency accesss * Firefox Attachment Workflow + Date Picker for custom timestamps * safari attach file Send req * excluded domains addition * fix tab titles * release notes * unlock articles * link to status feed * small typos * test * updated release notes * lastpass article form fill rewrites * import to org & personal clarifications * send self-hosting, safari web extension edits, and release notes
This commit is contained in:
fred_the_tech_writer
committed by
GitHub
GitHub
parent
7b16aceea1
commit
535ea72847
@@ -8,104 +8,139 @@ tags: [unlock, face id, touch id, hello, windows, mac, ios, android]
|
||||
order: 11
|
||||
---
|
||||
|
||||
Bitwarden can be configured to accept biometrics as a method to unlock your Vault. Biometrics can **only be used to unlock** your Vault, you will still be required to log in to your Vault with your Master Password and any enabled [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}).
|
||||
Bitwarden can be configured to accept biometrics as a method to unlock your Vault.
|
||||
|
||||
Biometric features are part of the built-in security in your device and/or operating system. Bitwarden leverages native APIs to perform this validation, and as such **does not receive any biometrics information** from the device.
|
||||
Biometrics can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
|
||||
## Mobile Applications
|
||||
|
||||
Biometric Unlock is supported for both the Android (Google Play or FDroid) and iOS Mobile Applications:
|
||||
- For **Android**, via [fingerprint unlock](https://support.google.com/nexus/answer/6285273?hl=en){:target="\_blank"} or [face unlock](https://support.google.com/pixelphone/answer/9517039?hl=en){:target="\_blank"}.
|
||||
- For **iOS**, via [Touch ID](https://support.apple.com/en-us/HT201371){:target="\_blank"} and [Face ID](https://support.apple.com/en-us/HT208109){:target="\_blank"}.
|
||||
|
||||
### Enable Biometric Unlock in Mobile
|
||||
|
||||
Complete the following steps to enable Biometric Unlock in your Mobile App:
|
||||
|
||||
{% callout info %}
|
||||
Your Biometric method of choice must be enabled on your device or operating system **before** it can be enabled in Bitwarden.
|
||||
{% callout success %}
|
||||
Biometric features are part of the built-in security in your device and/or operating system. Bitwarden leverages native APIs to perform this validation, and therefore **Bitwarden does not receive any biometrics information** from the device.
|
||||
{% endcallout %}
|
||||
|
||||
1. Open your **Settings** tab.
|
||||
2. In the Security section, your available Biometrics options will be listed. Tap the Biometric method you would like to enable:
|
||||
## Enable Unlock with Biometrics
|
||||
|
||||
{% image /biometrics/ios_faceid.jpeg Enable Face ID in iOS%}
|
||||
Unlock with Biometrics can be enabled for Bitwarden on Mobile, Desktop, and Browser Extensions:
|
||||
|
||||
A green `Enabled` status will appear when activated. Once Biometric Unlock is enabled, your device will automatically prompt for your biometric data when unlocking the app.
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
|
||||
## Desktop Applications
|
||||
#### Enable for Mobile
|
||||
|
||||
Biometric Unlock is supported for both the Windows and macOS Desktop Applications:
|
||||
- For **Windows**, via [Windows Hello](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello){:target="\_blank"} using PIN, Facial Recognition, or [other hardware that meets Windows Hello biometric requirements](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello-biometric-requirements){:target="\_blank"}.
|
||||
- For **macOS**, via [Touch ID](https://support.apple.com/en-us/HT207054){:target="\_blank"}.
|
||||
Unlock with Biometrics is supported for Android (Google Play or FDroid) via [fingerprint unlock](https://support.google.com/nexus/answer/6285273?hl=en){:target="\_blank"} or [face unlock](https://support.google.com/pixelphone/answer/9517039?hl=en){:target="\_blank"}, and for iOS via [Touch ID](https://support.apple.com/en-us/HT201371){:target="\_blank"} and [Face ID](https://support.apple.com/en-us/HT208109){:target="\_blank"}.
|
||||
|
||||
### Enable Biometric Unlock in Desktop
|
||||
To enable Unlock with Biometrics for your Mobile device:
|
||||
|
||||
Complete the following steps to enable Biometric Unlock in your Desktop App:
|
||||
1. In your device's native settings (e.g. the iOS {% icon fa-cog %} **Settings** app), make sure your biometric method is turned on.
|
||||
2. In your Bitwarden app, open the {% icon fa-cogs %} **Settings** tab.
|
||||
3. Scroll down to the Security section and tap the biometrics option you want to enable. What's available on this screen is determined by your device's hardware capabilities and what you've enabled (**Step 1**), for example:
|
||||
|
||||
{% callout info %}
|
||||
Your Biometric method of choice must be enabled on your device or operating system **before** it can be enabled in Bitwarden.
|
||||
{% endcallout %}
|
||||
{% image /biometrics/ios_faceid.jpeg Enable Face ID in iOS%}
|
||||
|
||||
1. Open your **Settings** (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
2. In the Security section, your available Biometrics options will be listed as checkbox items. Check the Biometric method you would like to enable:
|
||||
Tapping the option should prompt you to input your biometric (i.e. face or thumb-print). A green `Enabled` status indicator (pictured above) will indicate when Unlock with Biometrics is successfully enabled.
|
||||
|
||||
{% image /biometrics/windows.png Configuring Hello in Windows %}
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
|
||||
{% callout info %}
|
||||
If you do not see the option to enable Windows Hello within the Desktop preferences, you may need to install the [Microsoft Visual C++ Redistributable](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads).
|
||||
{% endcallout %}
|
||||
#### Enable for Desktop
|
||||
|
||||
Once Biometric Unlock is enabled, a new button will be presented on the Unlock screen. Selecting this button (for example, **Unlock with Windows Hello**) will initiate unlock. You may at any time choose to unlock your Vault with your Master Password instead.
|
||||
Unlock with Biometrics is supported for Windows via [Windows Hello](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello){:target="\_blank"} using PIN, Facial Recognition, or [other hardware that meets Windows Hello biometric requirements](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello-biometric-requirements){:target="\_blank"} and for macOS via [Touch ID](https://support.apple.com/en-us/HT207054){:target="\_blank"}.
|
||||
|
||||
To enable Unlock with Biometrics for your Desktop app:
|
||||
|
||||
1. In your device's native settings (e.g. the macOS {% icon fa-cog %} **System Preferences** app), make sure your biometric method is turned on.
|
||||
|
||||
{% callout success%}Windows Users may need to install the [Microsoft Visual C++ Redistributable](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads){:target="\_blank"} before Windows Hello can be turned on in Desktop Preferences.{% endcallout %}
|
||||
2. In your Bitwarden app, open your Settings (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
3. Scroll down to the Security section and select the biometrics option you want to enable. What's available on this screen is determined by your device's hardware capabilities and what you've turned on (**Step 1**), for example:
|
||||
|
||||
{% image /biometrics/windows.png Unlock with Windows Hello %}
|
||||
|
||||
Once enabled, a new button will be presented on the Unlock screen:
|
||||
|
||||
{% image /biometrics/hello-unlock.png Unlock with Windows Hello %}
|
||||
|
||||
## Browser Extensions
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
|
||||
Biometric Unlock is supported for **Chromium-based** (e.g. Chrome, Edge) Bitwarden Browser Extensions by integration with a native Bitwarden Desktop App (the Desktop App must also be running the latest version). Through the Desktop App's access to Biometric APIs, Browser Extensions support Biometric Unlock:
|
||||
- For **Windows**, via [Windows Hello](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello){:target="\_blank"} using PIN, Facial Recognition, or [other hardware that meets Windows Hello biometric requirements](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello-biometric-requirements){:target="\_blank"}.
|
||||
- For **macOS**, via [Touch ID](https://support.apple.com/en-us/HT207054){:target="\_blank"}.
|
||||
#### About Biometrics in Browser Extensions
|
||||
|
||||
{% callout note %}
|
||||
**Biometric Unlock is currently not available for:**
|
||||
Unlock with Biometrics is supported for Extensions through an integration with the Bitwarden Desktop app. In practical terms, this means:
|
||||
|
||||
- Firefox Browser Extensions (keep an eye on the required up-stream enhancement to make `nativeMessaging` optional [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1630415){:target="\_blank"}).
|
||||
- Safari Browser Extensions.
|
||||
1. A Bitwarden Desktop app must be installed, logged in, and running in order to use Unlock with Biometrics for a Browser Extension. Additionally, you will need to enable Unlock with Biometrics in **Desktop** before proceeding.
|
||||
2. Browser Extensions support the same biometrics options as Desktop; for Windows via [Windows Hello](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello){:target="\_blank"} using PIN, Facial Recognition, or [other hardware that meets Windows Hello biometric requirements](https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/windows-hello-biometric-requirements){:target="\_blank"} and for macOS via [Touch ID](https://support.apple.com/en-us/HT207054){:target="\_blank"}.
|
||||
|
||||
Two things to bear in mind before enabling the integration are **Permissions** and **Supportability**, documented below:
|
||||
|
||||
##### Permissions
|
||||
|
||||
To facilitate this integration, your browser will ask you to accept a new permission for Bitwarden to `communicate with cooperating native applications`. This permission is safe, but **optional**, and will enable the integration that is required to enable Unlock with Biometrics.
|
||||
|
||||
Declining this permission will allow you to use the Browser Extension as normal, without Unlock with Biometrics functionality.
|
||||
|
||||
##### Supportability
|
||||
|
||||
Unlock with Biometrics is supported for Extensions on **Chromium-based** browsers (Chrome, Edge, Opera, Brave, etc.). Unlock with Biometrics is **currently not supported for**:
|
||||
|
||||
- Safari
|
||||
- Firefox (there's a required up-stream enhancement to make `nativeMessaging` optional, documented [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1630415){:target="\_blank"}).
|
||||
- Microsoft App Store Desktop Apps (a side-loaded Windows Desktop App, available at [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} will work fine).
|
||||
- Side-loaded MacOS Desktop Apps (an App Store Desktop app will work fine).
|
||||
|
||||
In the cases of FireFox and the Microsoft App Store, this is due to native messaging limitations (see [Native Messaging Permissions](#native-messaging-permissions)). In all cases, Bitwarden team is investigating and will provide updates as things progress.
|
||||
{% endcallout %}
|
||||
#### Enable for Browser Extensions
|
||||
|
||||
The Bitwarden Desktop Application must be installed, logged in, and running in order to use Biometric Unlock in a Browser Extension. Additionally, you will need to [enable Biometric Unlock in the desktop app](#enable-biometric-unlock-in-desktop) before proceeding.
|
||||
To enable Unlock with Biometrics for your Browser Extension:
|
||||
|
||||
### Native Messaging Permissions
|
||||
1. In your Bitwarden Desktop app, navigate to Settings (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
2. Scroll down to the Options section, and check the **Enable Browser Integration** box.
|
||||
|
||||
When your Chromium-based Browser Extension updates to the version that supports Biometric Unlock (v1.48.0), you may be asked to accept a new permission for Bitwarden to `Communicate with cooperating native applications`. This permission is safe, but **optional**, and will enable the Browser Extension to communicate with the Bitwarden Desktop App, which is required to enable Biometric Unlock, as described above.
|
||||
{% callout note %}Optionally, check the **Require verification for browser integration** option to require [account fingerprint]({% link _articles/features/fingerprint-phrase.md %}) verification when you activate the integration.{% endcallout %}
|
||||
3. In your Browser, navigate to the Extensions manager (e.g. `chrome://extensions` or `brave://extensions`), open Bitwarden, and toggle the **Allow access to file URLs** option.
|
||||
|
||||
{% callout success %}
|
||||
Some browsers may additionally require you to **Allow access to file URLs** for Browser Extension Biometrics to function properly.
|
||||
{% endcallout %}
|
||||
|
||||
Declining this permission will allow you to use v1.48.0 as normal, without Biometric Unlock functionality.
|
||||
Not all browsers will require this to be toggled on, so feel free to skip this step and circle back to it only if the remaining procedure doesn't work.
|
||||
4. In your Browser Extension, open the {% icon fa-cogs %} **Settings** tab.
|
||||
5. Scroll down to the Security section and check the **Unlock with biometrics** box.
|
||||
|
||||
### Enable Biometric Unlock for Browser Extensions
|
||||
{% callout success %}You may be prompted at this stage to allow Bitwarden to `communicate with cooperating native applications`. This permission is safe, but **optional** and solely enables the Browser Extension to communicate with Desktop as described above.{% endcallout %}
|
||||
|
||||
Complete the following steps to enable Biometric Unlock in your Browser Extension:
|
||||
You should be prompted by your Desktop app to input your biometric. Doing so will complete the initial setup procedure. If you've opted to require verification (**Step 2**), you'll need to approve a fingerprint validation check.
|
||||
|
||||
1. In the Desktop App, navigate to **Settings** (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
2. Check the **Enable Browser Integration** checkbox.
|
||||
Once enabled, a new button will be presented on the Unlock screen:
|
||||
|
||||
Optionally, enable the **Require verification for browser integration** option to require [account fingerprint]({% link _articles/features/fingerprint-phrase.md %}) verification when activating the integration between Browser Extension and Desktop App.
|
||||
3. In the Browser Extension, open the **Settings** tab.
|
||||
4. Check the **Unlock with biometrics** checkbox to activate the integration. You will be prompted by your Desktop App to input your biometric authentication method to complete the setup.
|
||||
{% image /biometrics/be-bio-unlock.png Unlock with Biometrics %}
|
||||
|
||||
If you've opted to **Require verification for browser integration**, a `Desktop sync verification` dialog box will appear in your Browser Extension and a `Verify browser connection` dialog box will appear in your Desktop Application. Validate that the displayed [account fingerprint]({% link _articles/features/fingerprint-phrase.md %}) matches in both locations. If they match, select the **Approve** button and input your Biometric authentication method.
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
{% callout success %}In either case, you'll need to redo this "activation" step each time the Desktop App or Browser Extension is restarted.{% endcallout %}
|
||||
## Understanding Unlock vs. Log In
|
||||
|
||||
Once Biometric Unlock is enabled, a new button will be presented on the Unlock screen. Selecting the **Unlock biometrics** button will initiate unlock via the Desktop App.
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({% link _articles/security/vault-data.md %}) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({% link _articles/security/what-encryption-is-used.md %}).
|
||||
|
||||
{% callout warning %}
|
||||
If you attempt to use Biometric Unlock when the Desktop App is closed, you will be prompted to open the Desktop App. If you've opted to **Require verification for browser integration**, you'll also be prompted to recomplete fingerprint verification.
|
||||
{% endcallout %}
|
||||
**Logging in** to Bitwarden **decrypts** your Vault data to your device. In practice, that means two things:
|
||||
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({% link _articles/two-step-login/setup-two-step-login.md %}) would be required.
|
||||
2. Logging in will always require you to be connected to the internet (or, if you're self-hosting, connected to the server), because you need access to the encrypted Vault in order to decrypt it.
|
||||
|
||||
**Unlocking** can only be done when you're already logged in. In other words, only when your Vault data is already decrypted to your device. Because your Vault is already decrypted:
|
||||
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({% link _articles/account/unlock-with-pin.md %}) and [biometrics]({% link _articles/account/biometrics.md %}).
|
||||
2. You don't need to be connected to the internet (or, if you're self-hosting, connected to the server).
|
||||
|
||||
@@ -8,11 +8,11 @@ tags: [export, accounts, csv]
|
||||
order: 06
|
||||
---
|
||||
|
||||
Bitwarden allows you to export your personal Vault data from any client application, or an Organization Vault from the Web Vault or CLI. Exports can be downloaded as plaintext `.json` or `.csv` files, or as a `.json` [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
You can export your personal Vault data from any client application, or export an Organization Vault from the Web Vault or CLI. Exports can be downloaded as plaintext `.json` or `.csv` files, or as a `.json` [encrypted export]({% link _articles/importing/encrypted-export.md %}).
|
||||
|
||||
Bitwarden recommends using `.json` for a more complete option for standard backup procedures as `.csv` exports will not export Cards or Identities. For information on the format of Bitwarden `.csv` and `.json` exports, see [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
We recommend using `.json` for a more complete export, as `.csv` files won't currently export Cards or Identities. For complete information on the format of Bitwarden `.csv` and `.json` files, see [Condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
|
||||
Vault Exports **will not include** File Attachments or Items in the Trash.
|
||||
Vault Exports **will not include** [file attachments]({% link _articles/features/attachments.md %}) or Items in the Trash.
|
||||
|
||||
{% callout warning %}
|
||||
Unless you're using an [Encrypted Export]({% link _articles/importing/encrypted-export.md %}), do not store or send the exported file over insecure channels, like email, and delete the file immediately after use.
|
||||
@@ -20,74 +20,153 @@ Unless you're using an [Encrypted Export]({% link _articles/importing/encrypted-
|
||||
|
||||
## Export a Personal Vault
|
||||
|
||||
Export your Personal Vault data from any client application:
|
||||
Export your personal Vault data from any client application:
|
||||
|
||||
### From the Web Vault
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab">
|
||||
{% capture web_vault %}
|
||||
|
||||
#### Export from the Web Vault
|
||||
|
||||
To export your personal Vault data from the Web Vault:
|
||||
|
||||
1. Select **Tools** from the top navigation bar.
|
||||
3. Select **Export Vault** from the left-hand Tools menu.
|
||||
4. On the Export Vault page:
|
||||
- Select a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
- Enter your **Master Password**.
|
||||
5. Select the **Export Vault** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
2. Select **Export Vault** from the left-hand Tools menu.
|
||||
3. On the Vault Export page, choose a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
4. Enter your **Master Password** and select the **Export Vault** button.
|
||||
|
||||
### From the Mobile App
|
||||
{% endcapture %}
|
||||
{{ web_vault | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
|
||||
1. Tap the **Settings** tab.
|
||||
2. Scroll down to the **Tools** section, and tap **Export Vault**.
|
||||
3. On the Export Vault page:
|
||||
- Select a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
- Enter your **Master Password**.
|
||||
4. Select the **Export Vault** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
#### Export from a Browser Extension
|
||||
|
||||
### From the Browser Extension
|
||||
To export your personal Vault data from a Browser Extension:
|
||||
|
||||
1. Open the **Settings** tab.
|
||||
2. Scroll down to the **Tools** section, and select **Export Vault**.
|
||||
4. On the Export Vault page:
|
||||
- Select a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
- Enter your **Master Password**.
|
||||
5. Select the **Export Vault** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
1. Open the {% icon fa-cogs %} **Settings** tab.
|
||||
2. Scroll down to the **Tools** section and select the **Export Vault** option.
|
||||
3. On the Export Vault view, choose a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
4. Enter your **Master Password** and select **Submit**.
|
||||
|
||||
### From the Desktop App
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
|
||||
1. Navigate to **File** → **Export Vault**.
|
||||
2. In the Export Vault window:
|
||||
- Select a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
- Enter your **Master Password**.
|
||||
3. Select the **Submit** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
#### Export from Desktop
|
||||
|
||||
### From the CLI
|
||||
To export your personal Vault data from a Desktop app:
|
||||
|
||||
Use the `bw export` command to export your Vault data. By default, `bw export` will create a `.csv` export in the current working directory.
|
||||
1. From the menu bar, navigate to **File** → **Export Vault**.
|
||||
2. In the Export Vault window, choose a **File Format** (`.json`, `.csv`, or `.json (Encryped)`).
|
||||
3. Enter your **Master Password** and select the {% icon fa-download %} **Download** button.
|
||||
|
||||
You may pass the following options with the `bw export` command:
|
||||
- `--output <filePath>` to specify a saving location of your choice.
|
||||
- `--format <format>` to specify the file format as `csv` (*default*), `json`, or `encrypted_json`.
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
|
||||
#### Export from Mobile
|
||||
|
||||
To export your personal Vault data from a Mobile app:
|
||||
|
||||
1. Tap the {% icon fa-cogs %} **Settings** tab.
|
||||
2. Scroll down to the **Tools** section and tap the **Export Vault** option.
|
||||
3. On the Export Vault view, choose a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
4. Enter your **Master Password** and tap the **Export Vault** button.
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab">
|
||||
{% capture cli_info %}
|
||||
|
||||
#### Export from the CLI
|
||||
|
||||
To export your personal Vault from the CLI, use the `export` command. By default, `export` will export your Vault as a `.csv` and save the file to the working directory, however this behavior can be altered using options:
|
||||
|
||||
```
|
||||
bw export my-master-password --output /users/me/documents/ --format json
|
||||
```
|
||||
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## Export an Organization Vault
|
||||
|
||||
Admins and Owners may export their Organization Vault from the Web Vault or CLI:
|
||||
Organization [Admins and Owners]({% link _articles/organizations/user-types-access-control.md %}) can export their Organization Vault (i.e. all items [shared in Collections]({% link _articles/organizations/share-to-a-collection.md %})) from the Web Vault or CLI:
|
||||
|
||||
### From the Web Vault
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="orgwvtab" data-target="#orgwebvault" role="tab" aria-controls="orgwebvault" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="orgclitab" data-target="#orgcli" role="tab" aria-controls="orgcli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="orgwebvault" role="tabpanel" aria-labelledby="orgwvtab">
|
||||
{% capture org_web_vault %}
|
||||
|
||||
1. Open your Organization and select the **Tools** tab.
|
||||
#### Export Org from the Web Vault
|
||||
|
||||
To export your Organization Vault data from the Web Vault:
|
||||
|
||||
1. Open your Organization and select the **Tools** tab:
|
||||
|
||||
{% image organizations/org-export.png Export Organization Vault %}
|
||||
2. Select **Export Vault** from the left-hand Tools menu.
|
||||
4. On the Export Vault page:
|
||||
- Select a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
- Enter your **Master Password**.
|
||||
5. Select the **Export Vault** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
4. On the Vault Export page, choose a **File Format** (`.json`, `.csv`, or `.json (Encrypted)`).
|
||||
4. Enter your **Master Password** and select the **Export Vault** button.
|
||||
|
||||
### From the CLI
|
||||
{% endcapture %}
|
||||
{{ org_web_vault | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="orgcli" role="tabpanel" aria-labelledby="orgclitab">
|
||||
{% capture org_cli_info %}
|
||||
|
||||
From the Bitwarden CLI application, use the `bw export` command with the `--organizationid <orgId>` option to export your Organization Vault.
|
||||
#### Export Org from the CLI
|
||||
|
||||
{% callout info %}
|
||||
Retrieve your `<orgId>` value using the command: `bw list organizations`.
|
||||
To export your Organization Vault from the CLI, use the `export` command with the `--organizationid` option.
|
||||
|
||||
By default, `export` will export your Vault as a `.csv` and save the file to the working directory, however this behavior can be altered using options:
|
||||
|
||||
```
|
||||
bw export my-master-password --organizationid 7063feab-4b10-472e-b64c-785e2b870b92 --output /users/me/documents/ --format json
|
||||
```
|
||||
|
||||
{% callout success %}
|
||||
If you don't know your `organizationid` value off-hand, you can access it at the command-line using `bw list organizations`.
|
||||
{% endcallout %}
|
||||
|
||||
By default, `bw export` will create a `.csv` export in the current working directory, however you may pass the following options with the command:
|
||||
- `--output <filePath>` to specify a saving location of your choice.
|
||||
- `--format <format>` to specify the file format as `csv` (*default*), `json`, or `encrypted_json`.
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
{% endcapture %}
|
||||
{{ org_cli_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -8,22 +8,22 @@ tags: [master password, account]
|
||||
order: 02
|
||||
---
|
||||
|
||||
As described in the [Your Master Password]({% link _articles/account/master-password.md %}) article, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password. If you've already lost your Master Password, there is unfortunately no way for the team to recover the account or the data therein. You will need to delete your account and start a new one.
|
||||
As described in the [Your Master Password]({% link _articles/account/master-password.md %}) article, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password.
|
||||
|
||||
If you've already lost your Master Password, there is unfortunately no way for the team to recover the account or the data therein. You will need to delete your account and start a new one.
|
||||
|
||||
{% callout success %}
|
||||
Before deleting your account:
|
||||
|
||||
**First**, use the [Get master password hint](https://vault.bitwarden.com/#/hint){:target="\_blank"} link if you have a hint setup. Hints will be emailed to the email address associated with your account. If you don't have a hint setup, you'll get an email reporting this.
|
||||
|
||||
**Second**, if you're using any Bitwarden client applications (Mobile Apps, Browser Extensions, etc.), you should check whether any of these sessions are still logged in prior to deleting your account. If a client application is still logged in, you should manually catalogue your Vault items to preserve your data.
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to delete your account:
|
||||
|
||||
{% callout warning%}
|
||||
This action is permanent and cannot be undone.
|
||||
{% endcallout %}
|
||||
If you weren't able to gain access to your Vault, complete the following steps to delete your account:
|
||||
|
||||
1. Navigate to [vault.bitwarden.com/#/recover-delete](https://vault.bitwarden.com/#/recover-delete).
|
||||
2. Enter the **Email Address** associated with your account.
|
||||
2. Enter the **Email Address** associated with your account and select **Submit**.
|
||||
3. In your email inbox, open the email and verify that you want to delete this Bitwarden account.
|
||||
|
||||
Once deleted, you're free to create a new Bitwarden account with that email address. If you delete a Bitwarden account that has a Premium subscription associated with it, [Contact Us](https://bitwarden.com/contact/){:target="\_blank"} and we'll reapply your existing subscription to the new account.
|
||||
|
||||
@@ -1,27 +1,23 @@
|
||||
---
|
||||
layout: article
|
||||
title: Bitwarden Safari App Extension
|
||||
title: Safari Web Extension
|
||||
categories: [miscellaneous]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [browser, safari]
|
||||
---
|
||||
|
||||
## Get the Extension
|
||||
Bitwarden's Safari Web Extension is a port of the prior *App Extension* designed for use with [Safari 14](https://developer.apple.com/documentation/safariservices/safari_web_extensions/converting_a_safari_app_extension_to_a_safari_web_extension?language=objc){:target="\_blank"}. The Safari Web Extension is packaged with the Bitwarden Desktop App available on the App Store.
|
||||
|
||||
Bitwarden's Safari App Extension is packaged with the Bitwarden Desktop App available on the App Store, as recommended by from Apple regarding Safari App Extensions.
|
||||
|
||||
{% callout warning %}
|
||||
Due to changes by Apple, Safari now limits Safari App Extension use to only those obtained through Mac App Store downloads. As of Q1 2021, users will not be able to use a Bitwarden Safari App Extension obtained through a `.dmg` installation from [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} or any other non-App Store source.
|
||||
|
||||
To read community conversation on the topic, refer to the following Apple Developer Forum threads ([Thread #1](https://developer.apple.com/forums/thread/659029){:target="\_blank"}, [Thread #2](https://developer.apple.com/forums/thread/667859){:target="\_blank"}).
|
||||
{% callout info %}
|
||||
Due to changes by Apple, Safari limits Web Extension use to **only those obtained through Mac App Store downloads**. As of the [2021-03-11 Release]({% link _articles/getting-started/releasenotes.md %}), users will not be able to use a Bitwarden Safari Extension obtained through a `.dmg` installation from [bitwarden.com/download](https://bitwarden.com/download){:target="\_blank"} or any other non-App Store source.
|
||||
{% endcallout %}
|
||||
|
||||
For developer detail on Safari App Extensions, click [here](https://developer.apple.com/documentation/safariservices/safari_app_extensions).
|
||||
The Safari Web Extension has full feature parity to the prior App Extension. For developer detail on the difference between Safari Web Extensions and App Extensions, click [here](https://developer.apple.com/documentation/safariservices/safari_web_extensions/converting_a_safari_app_extension_to_a_safari_web_extension?language=objc).
|
||||
|
||||
## Enable the Extension
|
||||
|
||||
Before enabling the Safari App Extension, run the Desktop Application at least once. In Safari:
|
||||
Before enabling the Safari Web Extension, run the Desktop Application at least once. In Safari:
|
||||
|
||||
1. Open the **Preferences** window.
|
||||
2. Navigate to the **Extensions** page.
|
||||
|
||||
@@ -8,15 +8,14 @@ tags: [account, items, import, delete, trash, clone]
|
||||
order: 03
|
||||
---
|
||||
|
||||
Bitwarden can store 4 types of items in your Vault:
|
||||
Effectively managing the items in your Vault is key to making sure that you secure and have seamless access to your information, and can safely share information with friends, family, teams, and colleagues.
|
||||
|
||||
Bitwarden can store 4 types of items in your Vault:
|
||||
- [Logins](#logins)
|
||||
- [Cards](#cards)
|
||||
- [Identities](#identities)
|
||||
- [Secure Notes](#secure-notes)
|
||||
|
||||
Effectively managing the items in your Vault is key to making sure that you secure and have seamless access to your information, and can safely share information with friends, family, teams, and colleagues.
|
||||
|
||||
## Add a Vault Item
|
||||
|
||||
You can add items to your Vault from the Bitwarden [Web Vault](https://vault.bitwarden.com){:target="\_blank"} or any client application. Look for a {% icon fa-plus %} **Add** icon to add an item to your Vault. There are 4 types of items you can add to your Vault.
|
||||
|
||||
@@ -10,7 +10,7 @@ redirect_from:
|
||||
- /article/change-your-master-password/
|
||||
---
|
||||
|
||||
## About Your Master Password
|
||||
## About your Master Password
|
||||
|
||||
Your Master Password is the primary method for accessing your Vault. It's critically important that your Master Password is:
|
||||
|
||||
@@ -31,35 +31,40 @@ If you're worried about forgetting your Master Password, the team at Bitwarden h
|
||||
|
||||
{% endcallout %}
|
||||
|
||||
## Changing Your Master Password
|
||||
## Change your Master Password
|
||||
|
||||
You can change your Master Password at any time from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}, **provided you know you current Master Password** (if you don't, see [I Forgot My Master Password](#i-forgot-my-master-password)).
|
||||
Provided you **know your current Master Password**, change your Master Password at any time from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"}.
|
||||
2. Select the **Settings** tab from the top navigation.
|
||||
3. On the **My Account** page, scroll down and locate the **Change Master Password** section.
|
||||
4. Enter your **Current Master Password**.
|
||||
5. Enter and Confirm your **New Master Password**.
|
||||
6. Select the **Change Master Password** button.
|
||||
|
||||
Completing these steps will log you out of your current session, requiring you to log back in with you new Master Password. Currently logged-in client applications (Mobile Apps, Browser Extensions, etc.) may remain active for up to an hour, however they will eventually also require you to log back in with your new Master Password.
|
||||
|
||||
{% callout warning %}
|
||||
Opting to **rotate account's encryption key** is a potentially dangerous operation. Read the article on [Account Encryption Keys]({% link _articles/account/account-encryption-key.md %}) before doing so to fully understand the ramifications and required follow-up procedures.
|
||||
{% callout success %}
|
||||
If you don't know your Master Password, see [I Forgot my Master Password]({% link _articles/account/forgot-master-password.md %}).
|
||||
{% endcallout %}
|
||||
|
||||
## I Forgot My Master Password
|
||||
1. In your Web Vault, Select the **Settings** tab from the top navigation.
|
||||
2. On the **My Account** page, scroll down to the **Change Master Password** section.
|
||||
3. Enter your **Current Master Password**.
|
||||
4. Enter and Confirm your **New Master Password**.
|
||||
|
||||
As described in the [About Your Master Password](#about-your-master-password) section, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password. If you've already lost your Master Password, there is unfortunately no way for the team to recover the account or the data therein. You will need to delete your account and start a new one.
|
||||
{% callout warning %}Don't check the **rotate account's encryption key** box unless you fully understand the ramifications and required follow-up procedures. Learn more [here]({% link _articles/account/account-encryption-key.md %}).{% endcallout %}
|
||||
5. Select the **Change Master Password** button.
|
||||
|
||||
Changing your Master Password will log you out of your current Web Vault session, requiring you to log back in with your new Master Password.
|
||||
|
||||
Other logged-in client applications (Mobile Apps, Browser Extensions, etc.) may remain active for up to an hour, however they will eventually also require you to log back in with your new Master Password.
|
||||
|
||||
## I forgot my Master Password
|
||||
|
||||
As described in the [About Your Master Password](#about-your-master-password) section, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password.
|
||||
|
||||
If you've already lost your Master Password, there is unfortunately no way for the team to recover the account or the data therein. You will need to delete your account and start a new one.
|
||||
|
||||
{% callout success %}
|
||||
If you're using any Bitwarden client applications (Mobile Apps, Browser Extensions, etc.) you should check whether any of these sessions are still logged in prior to deleting your account. If a client application is still logged in, you should manually catalogue your Vault items to preserve your data.
|
||||
{% endcallout %}
|
||||
|
||||
Complete the following steps to delete your account:
|
||||
To delete your account:
|
||||
|
||||
1. Navigate to [vault.bitwarden.com/#/recover-delete](https://vault.bitwarden.com/#/recover-delete).
|
||||
2. Enter the **Email Address** associated with your account.
|
||||
2. Enter the **Email Address** associated with your account and select **Submit**.
|
||||
3. In your email inbox, open the email and verify that you want to delete this Bitwarden account.
|
||||
|
||||
Once deleted, you're free to create a new Bitwarden account with that email address. If you delete a Bitwarden account that has a Premium subscription associated with it, [Contact Us](https://bitwarden.com/contact/){:target="\_blank"} and we'll reapply your existing subscription to the new account.
|
||||
|
||||
@@ -8,50 +8,90 @@ tags: [unlock, pin]
|
||||
order: 10
|
||||
---
|
||||
|
||||
Bitwarden can be configured to accept a Personal Identification Number (PIN) as a method to unlock your Vault. PINs can **only be used to unlock** your Vault, you will still be required to log in to your Vault with your Master Password and any enabled [Two-step Login Method]({% link _articles/two-step-login/setup-two-step-login.md %}).
|
||||
Bitwarden can be configured to accept a Personal Identification Number (PIN) as a method to unlock your Vault.
|
||||
|
||||
PINs can **only be used to unlock** your Vault, you will still be required to use your Master Password and any enabled [Two-step Login method]({% link _articles/two-step-login/setup-two-step-login.md %}) when you **log in**. If you're not sure of the difference, scroll down to [Understanding Unlock vs. Log In](#understanding-unlock-vs-log-in).
|
||||
|
||||
## Enable Unlock with PIN
|
||||
|
||||
Unlock with PIN can be enabled for Bitwarden Browser Extensions, Mobile Apps, and Desktop Apps:
|
||||
Unlock with PIN can be enabled for Bitwarden Browser Extensions, Desktop, and Mobile:
|
||||
|
||||
### Enable for Browser Extensions
|
||||
|
||||
Complete the following steps to enable Unlock with PIN in your Browser Extension:
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
|
||||
#### Enable for Browser Extension
|
||||
|
||||
To enable Unlock with PIN for your Browser Extension:
|
||||
|
||||
1. Open the {% icon fa-cogs %} **Settings** tab.
|
||||
2. In the Security section, check the **Unlock with PIN** checkbox.
|
||||
3. Enter the desired PIN code in the input box. PIN codes can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
2. Scroll down to the Security section and check the **Unlock with PIN** checkbox.
|
||||
3. Enter the desired PIN code in the input box. Your PIN can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
|
||||
{% callout success %}**Optional:** The pre-checked option **Lock with master password on browser restart** will require you to enter your Master Password instead of a PIN when your browser restarts. If you want to be able to unlock with a PIN when your browser restarts, uncheck this option.{% endcallout %}
|
||||
{% callout success %}The pre-checked option **Lock with master password on browser restart** will require you to enter your Master Password instead of the PIN when your browser restarts. If you want the ability to unlock with a PIN even when the browser restarts, uncheck the option.{% endcallout %}
|
||||
|
||||
Regardless of whether you use the **Lock with master password on browser restart** option, your PIN settings will remain until you **log out** of Bitwarden.
|
||||
Your Unlock with PIN settings will persist **until you log out**. When you log out of your Browser Extension, you'll need to re-enable Unlock with PIN.
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
|
||||
Once enabled, you'll be prompted to **Verify PIN** to unlock the Browser Extension.
|
||||
#### Enable for Desktop
|
||||
|
||||
### Enable for Desktop Apps
|
||||
|
||||
Complete the following steps to enable Unlock with PIN in your Browser Extension:
|
||||
To enable Unlock with PIN for your Desktop app:
|
||||
|
||||
1. Open your **Settings** (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
2. In the Security section, check the **Unlock with PIN** checkbox.
|
||||
3. Enter the desired PIN code in the input box. PIN codes can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
2. Scroll down to the Security section and check the **Unlock with PIN** checkbox.
|
||||
3. Enter the desired PIN code in the input box. Your PIN can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
|
||||
{% callout success %}**Optional:** The pre-checked option **Lock with master password on restart** will require you to enter your Master Password instead of a PIN when your app restarts. If you want to be able to unlock with a PIN when your app restarts, uncheck this option.{% endcallout %}
|
||||
{% callout success %}The pre-checked option **Lock with master password on restart** will require you to enter your Master Password instea of the PIN when the app restarts. If you want the ability to unlock with a PIN when the app restarts, uncheck this option.{% endcallout %}
|
||||
|
||||
Regardless of whether you use the **Lock with master password on restart** option, your PIN settings will remain until you **log out** of Bitwarden.
|
||||
Your Unlock with PIN settings will persist **until you log out**. When you log out of your Desktop App, you'll need to re-enable Unlock with PIN.
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
|
||||
Once enabled, you'll be prompted to **Verify PIN** to unlock the Desktop App.
|
||||
#### Enable for Mobile
|
||||
|
||||
### Enable for Mobile Apps
|
||||
|
||||
Complete the following steps to enable Unlock with PIN in your Browser Extension:
|
||||
To enable Unlock with PIN for your Mobile app:
|
||||
|
||||
1. Open the {% icon fa-cogs %} **Settings** tab.
|
||||
2. In the Security section, tap the **Unlock with PIN code** option.
|
||||
3. Enter the desired PIN code in the input box and tap **Submit**. PIN codes can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
2. Scroll down to the Security section and tap the **Unlock with PIN Code** option.
|
||||
3. Enter the the desired PIN code in the input box. Your PIN can be any combination of characters (a-z, 0-9, $, #, etc.).
|
||||
|
||||
{% callout success %}A dialog box will appear asking `Do you want to require unlocking with your master password when the application is restarted?` Tap **Yes** to require you to enter your Master Password instead of a PIN after your apps restarts. Tap **No** to be able to unlock with a PIN after your app restarts.{% endcallout %}
|
||||
{% callout success %}A dialog box will appear asking whether you want to require unlocking with your master password when the application is restarted. Tap **Yes** to require your Master Password instead of PIN when the app restarts. Tap **No** for the ability to unlock with the PIN when the app restarts.{% endcallout %}
|
||||
|
||||
Regardless of whether you use the **Lock with master password on app restart** option, your PIN settings will remain until you **log out** of Bitwarden.
|
||||
Your Unlock with PIN settings will persist **until you log out**. When you log out of your Mobile App, you'll need to re-enable Unlock with PIN.
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Once enabled, you'll be prompted to **Verify PIN** to unlock the Mobile App.
|
||||
## Understanding Unlock vs. Log In
|
||||
|
||||
In order to understand why unlocking and logging in aren't the same, it's important to remember that Bitwarden [never stores unencrypted data]({% link _articles/security/vault-data.md %}) on its servers. **When your Vault is neither unlocked nor logged in**, your Vault data only exists on the server in its [encrypted form]({% link _articles/security/what-encryption-is-used.md %}).
|
||||
|
||||
**Logging in** to Bitwarden **decrypts** your Vault data to your device. In practice, that means two things:
|
||||
|
||||
1. Logging in will always require your Master Password, because your Master Password is the source of the key needed to decrypt your Vault data. Additionally, because decryption is an operation that needs to be protected, this stage is where [any enabled Two-step Login methods]({% link _articles/two-step-login/setup-two-step-login.md %}) would be required.
|
||||
2. Logging in will always require you to be connected to the internet (or, if you're self-hosting, connected to the server), because you need access to the encrypted Vault in order to decrypt it.
|
||||
|
||||
**Unlocking** can only be done when you're already logged in. In other words, only when your Vault data is already decrypted to your device. Because your Vault is already decrypted:
|
||||
|
||||
1. You don't need the decryption key derived from your Master Password, so you're free to use other access methods, like [PIN codes]({% link _articles/account/unlock-with-pin.md %}) and [biometrics]({% link _articles/account/biometrics.md %}).
|
||||
2. You don't need to be connected to the internet (or, if you're self-hosting, connected to the server).
|
||||
|
||||
@@ -26,7 +26,7 @@ Directory Connector configuration will vary based on the directory type in use.
|
||||
- [Sync with OneLogin]({% link _articles/directory-connector/onelogin-directory.md %})
|
||||
|
||||
{% callout info %}
|
||||
If you're using a self-hosted version of Bitwarden, you must change the Server URL used by the Directory Connector application:
|
||||
**If you're using a self-hosted version of Bitwarden**, you must change the Server URL used by the Directory Connector application:
|
||||
|
||||
1. Log out of Directory Connector.
|
||||
2. On the Login screen, select the **Settings** button.
|
||||
|
||||
@@ -47,3 +47,64 @@ Please note that storage of File Attachments is available only for Premium users
|
||||
- Purging your Vault before an import operation.
|
||||
|
||||
Personal Vaults can be purged from the **Settings** → **My Account** page. Organization Vaults can be purged from the **Organization Settings** → **My Organization** page.
|
||||
|
||||
### Q: What file formats does Bitwarden support for import?
|
||||
|
||||
**A:** The following formats are supported out-of-the-box:
|
||||
|
||||
{% callout info %}
|
||||
If your format is not listed below, manually [condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
{% endcallout %}
|
||||
|
||||
- [1Password (1pif)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Windows (.sv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Mac (csv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- Ascendo DataVault (csv)
|
||||
- Avast Passwords (csv)
|
||||
- Avira (json)
|
||||
- BlackBerry Password Keeper (csv)
|
||||
- Blur (csv)
|
||||
- [Brave (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Chrome (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Clipperz (html)
|
||||
- Codebook (csv)
|
||||
- Dashlane (json)
|
||||
- Encryptr (csv)
|
||||
- Enpass (csv)
|
||||
- Enpass (json)
|
||||
- [Firefox (csv)]({% link _articles/importing/import-from-firefox.md %})
|
||||
- F-Secure KEY (fsk)
|
||||
- GNOME Passwords and Keys/Seahorse (json)
|
||||
- Kaspersky Password Manager (txt)
|
||||
- KeePass 2 (xml)
|
||||
- KeePassX (csv)
|
||||
- Keeper (csv)
|
||||
- [LastPass (csv)]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- LogMeOnce (csv)
|
||||
- Meldium (csv)
|
||||
- mSecure (csv)
|
||||
- Myki (csv)
|
||||
- [Microsoft Edge (Chromium) (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Opera (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Padlock (csv)
|
||||
- Passbolt (csv)
|
||||
- PassKeep (csv)
|
||||
- Passman (json)
|
||||
- Passpack (csv)
|
||||
- Password Agent (csv)
|
||||
- Password Boss (json)
|
||||
- Password Dragon (xml)
|
||||
- Password Safe (xml)
|
||||
- PasswordWallet (txt)
|
||||
- RememBear (csv)
|
||||
- RoboForm (csv)
|
||||
- SafeInCloud (xml)
|
||||
- SaferPass (csv)
|
||||
- SecureSafe (csv)
|
||||
- SplashID (csv)
|
||||
- Sticky Password (xml)
|
||||
- True Key (csv)
|
||||
- Universal Password Manager (csv)
|
||||
- [Vivaldi (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Yoti (csv)
|
||||
- Zoho Vault (csv)
|
||||
|
||||
39
_articles/faqs/send-faqs.md
Normal file
39
_articles/faqs/send-faqs.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
layout: article
|
||||
title: Send FAQs
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 08
|
||||
---
|
||||
|
||||
### Q: Why can't I create a file Send?
|
||||
|
||||
**A:** Use of text Sends is available to all Bitwarden users, however creation of file Sends is only available for Premium users, including members of a Paid Organization (Families, Teams, or Enterprise).
|
||||
|
||||
### Q: Why can't I create a file Send from Firefox or Safari Browser Extension?
|
||||
|
||||
**A:** You can! But in order to browse for a file on the Create Send view in a Firefox Browser Extension, you'll need to open the extension in the sidebar or pop out a new window using the popout {% icon fa-external-link fa-rotate-270 %} button:
|
||||
|
||||
{% image /send/send-ff-popout.png The popout icon %}
|
||||
|
||||
### Q: Why are Sends missing from my Send view?
|
||||
|
||||
**A:** By design, Sends are ephemeral. Each created Send has a **maximum lifespan of 30 days**, configurable when you [create a Send]({% link _articles/send/create-send.md %}) or at any time by editing it. When a Send's [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) is reached, it will be purged from Bitwarden systems and inaccessible to both the Sender and any recipients.
|
||||
|
||||
### Q: What do the icons next to my Sends indicate?
|
||||
|
||||
**A:** Icons in the Send view are intended to help you understand the configured [lifespan]({% link _articles/send/send-lifespan.md %}) and [privacy]({% link _articles/send/send-privacy.md %}) options:
|
||||
|
||||
|Icon|Meaning|
|
||||
|----|-------|
|
||||
|{% icon fa-key %}|This Send is [protected by a password]({{site.baseurl}}/article/send-privacy/#send-passwords).|
|
||||
|{% icon fa-warning %}|This Send has been [manually disabled]({{site.baseurl}}/article/send-lifespan/#manually-disable-or-delete).|
|
||||
|{% icon fa-clock-o %}|This Send has reached it's specified [Expiration Date]({{site.baseurl}}/article/send-lifespan/#expiration-date).|
|
||||
|{% icon fa-ban %}|This Send has reached it's specified [Maximum Access Count]({{site.baseurl}}/article/send-lifespan/#maximum-access-count).|
|
||||
|{% icon fa-trash %}|This Send has reached it's specified [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) and is **Pending Deletion**.|
|
||||
|
||||
### Q: Can I prevent members of my Organization from using Send?
|
||||
|
||||
**A:** Enterprise Organizations can prevent their members from creating or editing Sends using the [Disable Send Policy]({{site.baseurl}}/article/policies/#disable-send).
|
||||
@@ -8,7 +8,7 @@ tags: [attachments, storage, files]
|
||||
order: 13
|
||||
---
|
||||
|
||||
Files can be attached to Vault items from any Bitwarden client application. An individual file attachment must be 100MB or smaller. By default, users have access to 1GB of encrypted storage for file attachments. Additional storage can be purchased in 1GB increments.
|
||||
Files can be attached to Vault items from any Bitwarden application. An individual file attachment must be 100MB or smaller. By default, paid users have access to 1GB of encrypted storage for file attachments. Additional storage can be purchased in 1GB increments.
|
||||
|
||||
{% callout info %}
|
||||
File Attachments are available for Premium users, including members of Paid Organizations (Families, Teams, or Enterprise).
|
||||
@@ -16,34 +16,107 @@ File Attachments are available for Premium users, including members of Paid Orga
|
||||
|
||||
## Attach a File
|
||||
|
||||
Complete the following steps to attach a file to a Vault item:
|
||||
To attach a file to a Vault item from a Bitwarden application:
|
||||
|
||||
### From the Web Vault
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link active" id="wvtab" data-bs-toggle="tab" data-target="#wv" role="tab" aria-controls="wv" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="betab" data-bs-toggle="tab" data-target="#be" role="tab" aria-controls="be" aria-selected="true">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-bs-toggle="tab" data-target="#mob" role="tab" aria-controls="mob" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-bs-toggle="tab" data-target="#desk" role="tab" aria-controls="desk" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-bs-toggle="tab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
1. Hover-over the item you'd like to attach a file to, and select the {% icon fa-cog %} **Gear** icon.
|
||||
2. Select **Attachments** from the dropdown.
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="wv" role="tabpanel" aria-labelledby="wvtab">
|
||||
{% capture be_sync %}
|
||||
### Attach from Web Vault
|
||||
|
||||
Complete the following steps to attach a file to a Vault item from the Web Vault:
|
||||
|
||||
1. Hover-over the Vault item you'd like to attach a file to, and select the {% icon fa-cog %} **Gear** icon.
|
||||
2. Select {% icon fa-paperclip %} **Attachments** from the dropdown.
|
||||
3. In the Attachments dialog box, **Browse...** for your file.
|
||||
4. Select the **Save** button to finish attaching a file.
|
||||
|
||||
Once an item has files attached, selecting **Attachments** from the {% icon fa-cog %} **Gear** dropdown will also display a list of files attached to that Vault item.
|
||||
Once a Vault item has a file attached to it, selecting {% icon fa-paperclip %} **Attachments** from the {% icon fa-cog %} **Gear** dropdown will also display a list of attached files.
|
||||
|
||||
### From Browser Extensions and Desktop Apps
|
||||
{% endcapture %}
|
||||
{{ be_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="be" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture be_sync %}
|
||||
### Attach from a Browser Extension
|
||||
|
||||
Complete the following steps to attach a file to a Vault item from a Bitwarden Browser Extension:
|
||||
|
||||
1. Open the item you'd like to attach a file to, and select the **Edit** button.
|
||||
2. Select **Attachments**.
|
||||
2. Select {% icon fa-paperclip %} **Attachments**.
|
||||
3. On the Attachments page/dialog, **Browse...** for your file.
|
||||
4. Select the **Save** button to finish attaching a file.
|
||||
|
||||
Once an item has files attached, selecting **Attachments** from the **Edit** menu will also display a list of files attached to that Vault item.
|
||||
Once a Vault item has a file attached to it, selecting {% icon fa-paperclip %} **Attachments** from will also display a list of attached files.
|
||||
|
||||
### From Mobile Apps
|
||||
{% endcapture %}
|
||||
{{ be_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="mob" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mob_sync%}
|
||||
### Attach from Mobile
|
||||
|
||||
Complete the following steps to attach a file to a Vault item from a Bitwarden Mobile App:
|
||||
|
||||
1. Open the item you'd like to attach a file to, and select the {% icon fa-ellipsis-v%} **Menu** button.
|
||||
2. Select **Attachments**.
|
||||
2. Select {% icon fa-paperclip %} **Attachments**.
|
||||
3. On the Attachments page, select the **Choose File** button and browse for your file.
|
||||
4. Select the **Save** button to finish attaching a file.
|
||||
|
||||
Once an item has files attached, selecting **Attachments** from the {% icon fa-ellipsis-v%} **Menu** will also display a list of files attached to that Vault item.
|
||||
Once a Vault item has a file attached to it, selecting {% icon fa-paperclip %} **Attachments** from the {% icon fa-ellipsis-v%} **Menu** dropdown will also display a list of attached files.
|
||||
|
||||
{% endcapture %}
|
||||
{{ mob_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="desk" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desk_sync%}
|
||||
### Attach from Desktop
|
||||
|
||||
Complete the following steps to attach a file to a Vault item from a Bitwarden Desktop App:
|
||||
|
||||
1. Open the item you'd like to attach a file to, and select the **Edit** button.
|
||||
2. Select {% icon fa-paperclip %} **Attachments**.
|
||||
3. On the Attachments page/dialog, **Browse...** for your file.
|
||||
4. Select the **Save** button to finish attaching a file.
|
||||
|
||||
Once a Vault item has a file attached to it, selecting {% icon fa-paperclip %} **Attachments** from will also display a list of attached files.
|
||||
|
||||
{% endcapture %}
|
||||
{{ desk_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="clitab">
|
||||
{% capture cli_sync%}
|
||||
### Attach from the CLI
|
||||
|
||||
Use `bw create attachment` to attach a file to an existing Vault item, for exaple:
|
||||
|
||||
```
|
||||
bw create attachment --file /path/to/myfile.ext --itemid <itemid>
|
||||
```
|
||||
|
||||
For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_sync | markdownify }}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## View an Attachment
|
||||
|
||||
|
||||
@@ -15,19 +15,19 @@ We're thrilled to be a part of your secure password management journey. To creat
|
||||
|
||||
## Create Account Screen
|
||||
|
||||
Once you've clicked the link, the following screen will appear:
|
||||
Once you've clicked the link, the following screen will appear. Fill out all fields (*Master Password Hint* is optional) and click **Submit** when you're finished.
|
||||
|
||||
{% image /getting-started/create-account-screen-overlay.png Create Account screen%}
|
||||
|
||||
Fill out all fields (*Master Password Hint* is optional) and click **Submit** when you're finished.
|
||||
|
||||
## Verify Your Email
|
||||
|
||||
Once you've created your account, prompt Bitwarden to send you a verification email by logging in to your [Web Vault](https://vault.bitwarden.com/) and selecting the **Verify Email** button located at near the top right.
|
||||
|
||||
## Congratulations!
|
||||
|
||||
For help getting going with Bitwarden, we recommend:
|
||||
- [Getting Started with the Browser Extension]({% link _articles/getting-started/getting-started-browserext.md %})
|
||||
- [Getting Started with the Mobile Apps]({% link _articles/getting-started/getting-started-mobile.md %})
|
||||
- [Bitwarden 101 Video Series - Getting Started](https://bitwarden.com/help/article/getting-started-videos/)
|
||||
We recommend using any one of these resources to learn the ropes:
|
||||
- [Get Started with the Web Vault]({% link _articles/getting-started/getting-started-webvault.md %})
|
||||
- [Get Started with Browser Extensions]({% link _articles/getting-started/getting-started-browserext.md %})
|
||||
- [Get Started with the Mobile Apps]({% link _articles/getting-started/getting-started-mobile.md %})
|
||||
- [Get Started with Desktop Apps]({% link _articles/getting-started/getting-started-desktop.md %})
|
||||
- [Bitwarden 101 Video Series on Getting Started](https://bitwarden.com/help/article/getting-started-videos/)
|
||||
|
||||
@@ -21,7 +21,7 @@ When your first log in to your Web Vault, you'll land on the **My Vault** view.
|
||||
|
||||
In the above screenshot, your **My Vault** view is showing {% icon fa-th %} **All Items**. The **Filters** column on the left-hand side of the Vault can help you use **Favorites** and **Folders** to organize your Vault so that you can quickly find whatever you're looking for.
|
||||
|
||||
Let's start by setting up a new Folder and adding a new Login Vault item to it:
|
||||
Let's start by setting up a new Folder and adding a new Login item to it:
|
||||
|
||||
#### Create a Folder
|
||||
|
||||
@@ -54,7 +54,7 @@ To add a new Login item:
|
||||
|
||||
Now that a new Login item is saved in your Vault, you can beef up its security by replacing the existing password with a stronger one:
|
||||
|
||||
1. In your Bitwarden Vault open, click on the item you want to secure to view its information.
|
||||
1. In your Bitwarden Vault, click on the item you want to secure to view its information.
|
||||
2. In a new tab or window, open the corresponding website and login to your account.
|
||||
|
||||
{% callout success %}If you entered something in the **URI 1** field, click the {% icon fa-share %} **Launch** icon to open it directly from your Vault!{% endcallout %}
|
||||
@@ -66,7 +66,7 @@ Now that a new Login item is saved in your Vault, you can beef up its security b
|
||||
You might have the old password memorized, but it's a good idea to get in the habit of copying and pasting your password since this is primarily how you'll be logging in to websites once your password is replaced with a stronger one.
|
||||
5. Tab back over to your Bitwarden Vault and click the {% icon fa-refresh %} **Generate** icon next to the **Password** field. You'll be asked whether you want to overwrite the current password, so click **Yes** to proceed.
|
||||
|
||||
This will replace your **Password** value with a randomly generated strong password. Moving from a password like `Fido1234` to `X@Ln@x9J@&u@5n##B` can stop would-be hacker in their tracks.
|
||||
This will replace your **Password** value with a randomly generated strong password. Moving from a password like `Fido1234` to `X@Ln@x9J@&u@5n##B` can stop a would-be hacker in their tracks.
|
||||
6. Copy your new password with the same {% icon fa-copy %} **Copy** icon you used earlier, and hit the **Save** button.
|
||||
|
||||
{% callout success %}Don't worry about overwriting your existing password! If something goes wrong, Bitwarden maintains a **Password History** for every Login item:<br><br>{% image /getting-started/pwhistory.png %}{% endcallout %}
|
||||
|
||||
@@ -23,7 +23,17 @@ Bitwarden believes source code transparency is an absolute requirement for secur
|
||||
|
||||
**Dates on this page represent Cloud Server and Web releases.** Bitwarden incrementally updates each client application (Desktop, Browser Extension, Mobile, etc.) following the initial release date to ensure feature efficacy and stability. As a result, client applications should expect listed features following the initial release.
|
||||
|
||||
To be notified of Release Announcements, subscribe to the Bitwarden Status RSS feed:
|
||||
To be notified of Release Announcements, subscribe to the [Bitwarden Status RSS Feed](https://status.bitwarden.com/){:target="\_blank"}.
|
||||
|
||||
## 2021-03-11
|
||||
|
||||
Bitwarden is proud to announce the release of Bitwarden Send, and end-to-end encrypted solution for ephemeral sharing. This release includes:
|
||||
|
||||
- **Bitwarden Send**: Bitwarden Send is end-to-end encrypted solution for ephemeral sharing. There's lot of material about Send on our website and Help Center, but you can start [here]({% link _articles/send/about-send.md %}).
|
||||
- **FIDO U2F Support for Edge**: Two-step Login via FIDO U2F is now available for the Web Vault and Browser Extensions in Microsoft Edge (see [here]({% link _articles/two-step-login/setup-two-step-login-u2f.md %}) for details).
|
||||
- **Domain Exclusion in Browser Extensions**: Bitwarden Browser Extensions can now be configured with domains to explicitly not offer to remember passwords for (see [here]({% link _articles/miscellaneous/exclude-domains.md %}) for details).
|
||||
- **Improved Import Error Messages**: We've had lots of folks migrating to Bitwarden recently, so we cleaned up an import error message to help you reconcile issues faster (see [here]({{site.baseurl}}/article/import-data/#length-related-import-errors) for details).
|
||||
- **Safari Web Extension Port**: Our Safari App Extension has officially been ported to a Web Extension for use with Safari 14+. Due to changes to Safari, Web Extension use is now limited to only those obtained through Mac App Store downloads (see [here]({% link _articles/account/install-safari-app-extension.md %}) for details).
|
||||
|
||||
## 2021-01-19 Post-Release Update
|
||||
|
||||
|
||||
@@ -8,10 +8,10 @@ tags: [import]
|
||||
order: 07
|
||||
---
|
||||
|
||||
Encrypted Exports provide a secure long-term storage option for Vault data backups. Vault data is encrypted using your account's Encryption Key.
|
||||
Vault data can be [exported]({% link _articles/account/export-your-data.md %}) in an encrypted JSON file. These exports are encrypted using your [account's encryption key]({% link _articles/account/account-encryption-key.md %}), which are generated on account creation and unique to each Bitwarden user account.
|
||||
|
||||
{% callout warning %}
|
||||
[Rotating your account's encryption key]({% link _articles/account/account-encryption-key.md %}) will render an Encrypted Export impossible to decrypt. **If you rotate your account encryption key, replace the old backup with one that uses the new encryption key.**
|
||||
[Rotating your account's encryption key]({% link _articles/account/account-encryption-key.md %}) will render an Encrypted Export impossible to decrypt. **If you rotate your account encryption key, replace any old files with new one that use the new encryption key.**
|
||||
|
||||
Account Encryption Keys are unique to each Bitwarden user account, so you won't be able to import an Encrypted Export into a different account.
|
||||
{% endcallout %}
|
||||
@@ -42,29 +42,113 @@ Will look something like:
|
||||
|
||||
## Create an Encrypted Export
|
||||
|
||||
Downloading an Encrypted Export follows the same procedure as downloading a plaintext `.csv` or `.json` export:
|
||||
Creating an Encrypted Export follows the [normal export procedure]({% link _articles/account/export-your-data.md %}):
|
||||
|
||||
1. In the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}, select **Tools** from the top navigation bar.
|
||||
3. Select **Export Vault** from the left-hand Tools menu.
|
||||
4. On the Export Vault page:
|
||||
- Select **.json (Encrypted)** from the **File Format** dropdown.
|
||||
- Enter your **Master Password**.
|
||||
5. Select the **Export Vault** button to download your Vault Export. You will be prompted to specify a location for download.
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab">
|
||||
{% capture web_vault %}
|
||||
|
||||
For help downloading an Encrypted Export from any other client application, see [Export Vault Data]({% link _articles/account/export-your-data.md %}).
|
||||
#### Export from the Web Vault
|
||||
|
||||
To create an encrypted export of your personal Vault data from the Web Vault:
|
||||
|
||||
1. Select **Tools** from the top navigation bar.
|
||||
2. Select **Export Vault** from the left-hand Tools menu.
|
||||
3. On the Vault Export page, choose `.json (Encrypted)` for the **File Format**.
|
||||
4. Enter your **Master Password** and select the **Export Vault** button.
|
||||
|
||||
{% endcapture %}
|
||||
{{ web_vault | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
|
||||
#### Export from a Browser Extension
|
||||
|
||||
To create an encrypted export of your personal Vault data from a Browser Extension:
|
||||
|
||||
1. Open the {% icon fa-cogs %} **Settings** tab.
|
||||
2. Scroll down to the **Tools** section and select the **Export Vault** option.
|
||||
3. On the Export Vault view, choose `.json (Encrypted)` for the **File Format**.
|
||||
4. Enter your **Master Password** and select **Submit**.
|
||||
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
|
||||
#### Export from Desktop
|
||||
|
||||
To create an encrypted export of your personal Vault data from a Desktop app:
|
||||
|
||||
1. From the menu bar, navigate to **File** → **Export Vault**.
|
||||
2. In the Export Vault window, choose `.json (Encrypted)` for the **File Format**.
|
||||
3. Enter your **Master Password** and select the {% icon fa-download %} **Download** button.
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
|
||||
#### Export from Mobile
|
||||
|
||||
To create an encrypted export of your personal Vault data from a Mobile app:
|
||||
|
||||
1. Tap the {% icon fa-cogs %} **Settings** tab.
|
||||
2. Scroll down to the **Tools** section and tap the **Export Vault** option.
|
||||
3. On the Export Vault view, choose `.json (Encrypted)` for the **File Format**.
|
||||
4. Enter your **Master Password** and tap the **Export Vault** button.
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab">
|
||||
{% capture cli_info %}
|
||||
|
||||
#### Export from the CLI
|
||||
|
||||
To create an encrypted export of your personal Vault data from the CLI, use the `export` command with the specified option `--format json_encrypted`, for example:
|
||||
|
||||
```
|
||||
bw export my-master-password --output /users/me/documents/ --format json_encrypted
|
||||
```
|
||||
|
||||
For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## Import an Encrypted Export
|
||||
|
||||
Importing an Encrypted Export following the same procedure as importing a plaintext `.csv` or `.json` file:
|
||||
Importing an Encrypted Export follows the [normal import procedure]({% link _articles/importing/import-data.md %}), which can **only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
|
||||
1. In the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}, select **Tools** from the top navigation bar.
|
||||
1. In the Web Vault, select **Tools** from the top navigation bar.
|
||||
2. Select **Import Data** from the left-hand Tools menu.
|
||||
3. Select **Bitwarden (json)** as the format of your file to import.
|
||||
3. From the format dropdown, choose **Bitwarden (json)**.
|
||||
|
||||
{% callout success %}There is no import option specifically for Encrypted Exports. A handler will determine that the `.json` file is encrypted and decrypt using your account encryption key.{% endcallout %}
|
||||
5. Select the **Browse** button and add your file.
|
||||
{% callout success %}There is no import option specifically for Encrypted Exports. A handler will determine that the `.json` file is encrypted and attempt to decrypt the file using your [account's encryption key]({% link _articles/account/account-encryption-key.md %}).{% endcallout %}
|
||||
5. Select the **Choose File** button and add the file to import.
|
||||
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
6. Select the **Import Data** button to complete your import.
|
||||
|
||||
{% callout warning %}
|
||||
Importing data multiple times will create duplicates.
|
||||
{% endcallout %}
|
||||
|
||||
@@ -8,120 +8,52 @@ tags: [import]
|
||||
order: 01
|
||||
---
|
||||
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your personal Vault or Organization Vault (see [Import Data to an Organization]({% link _articles/organizations/import-to-org.md %})).
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your personal Vault or Organization Vault. You can also use the data import tool to import from one Bitwarden Vault to another, or to import a Bitwarden [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
|
||||
You can also use the data import tool to import from one Bitwarden Vault to another, or to import a backup [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
|
||||
Bitwarden supports a large array of formats for import, including those used by the most popular password management solutions:
|
||||
For a full list of supported import formats, see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/send-faqs/#q-what-file-formats-does-bitwarden-support-for-import), or use one of these articles for importing from the most popular solutions:
|
||||
|
||||
- [Import from LastPass]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- [Import from 1Password]({% link _articles/importing/import-from-1password.md %})
|
||||
- [Import from Firefox]({% link _articles/importing/import-from-firefox.md %})
|
||||
- [Import from Google Chrome]({% link _articles/importing/import-from-chrome.md %})
|
||||
|
||||
For a full list of supported formats, see [Supported Formats](#supported-formats).
|
||||
|
||||
## Import to your Personal Vault
|
||||
|
||||
To import your data into a personal Vault:
|
||||
Importing data to Bitwarden **can only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank"}.
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}. Not already signed up? [Select a Bitwarden plan to get started.](https://bitwarden.com/pricing/business/)
|
||||
2. Select **Tools** from the top navigation bar.
|
||||
3. Select **Import Data** from the left Tools menu.
|
||||
4. Select the format of your file to import from the dropdown menu.
|
||||
{% callout success %}
|
||||
**Not already signed up?** Choose from one of [Bitwarden's plans](https://bitwarden.com/pricing/business/){:target="\_blank"} and get started today:
|
||||
|
||||
{% callout success%}If you're importing an [Encrypted Export]({% link _articles/importing/encrypted-export.md %}), select `.json` as you would if it were plaintext. A handler will determine that the file is encrypted and decrypt using your [account encryption key](https://bitwarden.com/help/article//change-your-master-password/#rotating-your-accounts-encryption-key).{% endcallout %}
|
||||
5. Select the **Browse** button and add your file.
|
||||
6. Select the **Import Data** button to complete your import.
|
||||
|
||||
{% callout warning %}
|
||||
Importing data multiple times will create duplicates.
|
||||
<a role="button" class="btn btn-primary" href="https://vault.bitwarden.com/#/register" target="blank">Create Your Free Account</a>
|
||||
{% endcallout %}
|
||||
|
||||
## Length-related Import Errors
|
||||
To import your data:
|
||||
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that a field in your import file exceeds the allowed **encrypted** character limit for that field type:
|
||||
1. In the Web Vault, select **Tools** from the top navigation bar.
|
||||
2. Select **Import Data** from the left-hand Tools menu.
|
||||
3. From the format dropdown, choose a **File Format** (see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/send-faqs/#q-what-file-formats-does-bitwarden-support-for-import)).
|
||||
|
||||
{% image /importing/ciphererrors.png Cipher errors in the Web Vault%}
|
||||
5. Select the **Choose File** button and add the file to import.
|
||||
|
||||
These error messages contain 3 pieces of pertinent data:
|
||||
- `Ciphers[X]` indicates the index number where the offending item is located.
|
||||
- `The field <field>` indicates the field name which is causing the offense.
|
||||
- `length of <limit> characters` indicates the character limit allowed for that field.
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
6. Select the **Import Data** button to complete your import.
|
||||
|
||||
{% callout note %}On import to Bitwarden, the character count of any given field is increased due to encryption, meaning that an 8000-character `note` field in your `.csv` will scale to 10,000+ characters when it comes into contact with Bitwarden, triggering this error. As a rule of thumb, character counts will grow between 30-50% when encrypted.{% endcallout %}
|
||||
## Troubleshooting
|
||||
|
||||
To solve this issue:
|
||||
### Length-related Import Errors
|
||||
|
||||
1. Open the `.csv` file you're attempting to import in a text editor or spreadsheet program.
|
||||
2. Locate the offending item at `index[X]`. The value of `X` references a `.csv` index number, so depending on the program you use to edit your file it may not map perfectly to a spreadsheet Row or Line number.
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
In many cases, you'll need to adjust for `.csv` header rows, which are not counted in many spreadsheet programs. It can also help to use field name (`yyyy`) and perceived character length as context clues.
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
{% callout success %}If you've having trouble locating the offending item using the data provided in the error, it may help to focus first on notes as these are frequently the cause of this error.{% endcallout %}
|
||||
3. Remove the offending item from your import file, or reduce the character count. When reducing the character count, remember that limits are placed on **encrypted** counts, not pre-encryption counts. As a rule of thumb, character counts will grow between 30-50% when Bitwarden attempts to encrypt a field on import.
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
## Supported Formats
|
||||
- `[1]` identifies the index number where the offending item is located, adjusted to match row numbering in *most* spreadsheet programs.
|
||||
- `[Login]` identifies the Vault item `type` of the offending item.
|
||||
- `"Facebook"` identifies the `name` of the offending item.
|
||||
- `Notes` indicates the field (column) where the character limit is exceeded.
|
||||
- `10000` indicates the character limit allowed for that field (column).
|
||||
|
||||
The following formats are supported out-of-the-box:
|
||||
{% callout success %}On import to Bitwarden, the character count of any given field is increased due to encryption, meaning that an 8000-character `Notes` field in your `.csv` will scale to 10,000+ characters when it comes into contact with Bitwarden, triggering this error. As a rule of thumb, character counts will grow between 30-50% when encrypted.{% endcallout %}
|
||||
|
||||
{% callout info %}
|
||||
If your format is not listed below, manually [condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
{% endcallout %}
|
||||
|
||||
- [1Password (1pif)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Windows (.sv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Mac (csv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- Ascendo DataVault (csv)
|
||||
- Avast Passwords (csv)
|
||||
- Avira (json)
|
||||
- BlackBerry Password Keeper (csv)
|
||||
- Blur (csv)
|
||||
- [Brave (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Chrome (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Clipperz (html)
|
||||
- Codebook (csv)
|
||||
- Dashlane (json)
|
||||
- Encryptr (csv)
|
||||
- Enpass (csv)
|
||||
- Enpass (json)
|
||||
- [Firefox (csv)]({% link _articles/importing/import-from-firefox.md %})
|
||||
- F-Secure KEY (fsk)
|
||||
- GNOME Passwords and Keys/Seahorse (json)
|
||||
- Kaspersky Password Manager (txt)
|
||||
- KeePass 2 (xml)
|
||||
- KeePassX (csv)
|
||||
- Keeper (csv)
|
||||
- [LastPass (csv)]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- LogMeOnce (csv)
|
||||
- Meldium (csv)
|
||||
- mSecure (csv)
|
||||
- Myki (csv)
|
||||
- [Microsoft Edge (Chromium) (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Opera (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Padlock (csv)
|
||||
- Passbolt (csv)
|
||||
- PassKeep (csv)
|
||||
- Passman (json)
|
||||
- Passpack (csv)
|
||||
- Password Agent (csv)
|
||||
- Password Boss (json)
|
||||
- Password Dragon (xml)
|
||||
- Password Safe (xml)
|
||||
- PasswordWallet (txt)
|
||||
- RememBear (csv)
|
||||
- RoboForm (csv)
|
||||
- SafeInCloud (xml)
|
||||
- SaferPass (csv)
|
||||
- SecureSafe (csv)
|
||||
- SplashID (csv)
|
||||
- Sticky Password (xml)
|
||||
- True Key (csv)
|
||||
- Universal Password Manager (csv)
|
||||
- [Vivaldi (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Yoti (csv)
|
||||
- Zoho Vault (csv)
|
||||
|
||||
#### Ready to get started?
|
||||
|
||||
<a role="button" class="btn btn-primary" href="https://vault.bitwarden.com/#/register">Create Your Free Account</a>
|
||||
If you continue to have trouble locating the offending item using the data provided in the error, it may help to focus first on notes as these are frequently the cause of this error.
|
||||
|
||||
@@ -12,7 +12,28 @@ Use this article for help exporting data from LastPass and importing into Bitwar
|
||||
|
||||
## Export from LastPass
|
||||
|
||||
Complete the following steps to export data from the [LastPass Web Vault](https://lastpass.com/){:target="\_blank"}:
|
||||
You can export your data from LastPass from their Web Vault or from a LastPass Browser Extension:
|
||||
|
||||
{% callout info %}
|
||||
A previous version of this article stated that you [needed to use the Browser Extension](https://support.logmeininc.com/lastpass/help/how-do-i-nbsp-export-my-lastpass-form-fill-profiles){:target="\_blank"} to export **Form Fills** (e.g. Addresses and Payment Cards), however testing by Bitwarden's Customer Success team found that using either LastPass application to download a standard **LastPass CSV** will include Form Fills in your export.
|
||||
{% endcallout %}
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="webtab" data-bs-toggle="tab" data-target="#web" role="tab" aria-controls="browsertab" aria-selected="true">LastPass Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="browsertab" data-bs-toggle="tab" data-target="#browser" role="tab" aria-controls="browsertab" aria-selected="false">LastPass Browser Extension</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="web" role="tabpanel" aria-labelledby="webtab">
|
||||
{% capture and_gs %}
|
||||
|
||||
#### From the LastPass Web Vault
|
||||
|
||||
To export your data from the LastPass Web Vault:
|
||||
|
||||
1. Select the {% icon fa-rocket %} **Advanced Options** option on the left sidebar:
|
||||
|
||||
@@ -31,11 +52,17 @@ Complete the following steps to export data from the [LastPass Web Vault](https:
|
||||
If you observe this bug in your exported data, use a text editor to find and replace all altered values before importing into Bitwarden.
|
||||
{% endcallout %}
|
||||
|
||||
### Export with Form Fills
|
||||
{% endcapture %}
|
||||
{{ and_gs | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="browser" role="tabpanel" aria-labelledby="browsertab">
|
||||
{% capture ios_gs %}
|
||||
|
||||
**Exports from the Web Vault will not include form fills.** To export form fill data from LastPass, you must do so from the Browser Extension:
|
||||
#### From a LastPass Browser Extension
|
||||
|
||||
1. In the Browser Extension, navigate to **Account Options** → **Advanced** → **Export** → **Form Fills**:
|
||||
To export your data from a LastPass Browser Extension:
|
||||
|
||||
1. In the Browser Extension, navigate to **Account Options** → **Advanced** → **Export** → **LastPass CSV File**:
|
||||
|
||||
{% image /importing/lp-be.png Export from Browser Extension %}
|
||||
2. Enter your Master Password to validate the export attempt.
|
||||
@@ -44,49 +71,46 @@ If you observe this bug in your exported data, use a text editor to find and rep
|
||||
{% image lastpass-copy.png LastPass Export %}
|
||||
4. If your Vault data was printed to the screen, highlight the text and copy and paste it into a new `export.csv` file.
|
||||
|
||||
|
||||
{% endcapture %}
|
||||
{{ ios_gs | markdownify }}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## Import to Bitwarden
|
||||
|
||||
Complete the following steps to import data to your Bitwarden personal Vault. For help importing to an Organization Vault, see [Import Items to an Organization]({% link _articles/organizations/import-to-org.md %}).
|
||||
Importing data to Bitwarden **can only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank"}. To import your data:
|
||||
|
||||
If you want to store File Attachments in your Bitwarden Vault, please be aware that these are currently not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({% link _articles/features/attachments.md %}).
|
||||
1. In the Web Vault, select **Tools** from the top navigation bar.
|
||||
2. Select **Import Data** from the left-hand Tools menu.
|
||||
3. From the format dropdown, choose **LastPass (csv)** from the File Format dropdown.
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}.
|
||||
2. Select **Tools** from the top navigation bar.
|
||||
3. Select **Import Data** from the left Tools menu.
|
||||
4. Select **LastPass (csv)** from the format dropdown.
|
||||
5. Select the **Browse...** button and add the file exported from LastPass.
|
||||
6. Select the **Import Data** button to complete your import.
|
||||
5. Select the **Choose File** button and add the file to import.
|
||||
|
||||
{% callout warning %}
|
||||
Importing data multiple times will create duplicates.
|
||||
{% endcallout %}
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
6. Select the **Import Data** button to complete your import.
|
||||
|
||||
Congratulations! You have just transferred your data from LastPass into Bitwarden.
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({% link _articles/features/attachments.md %}).
|
||||
|
||||
## Import Troubleshooting
|
||||
|
||||
### Character Limit Error
|
||||
### Length-related Import Errors
|
||||
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that a field in your import file exceeds the allowed **encrypted** character limit for that field type:
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
{% image /importing/ciphererrors.png Cipher errors in the Web Vault%}
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
These error messages contain 3 pieces of pertinent data:
|
||||
- `Ciphers[X]` indicates the index number where the offending item is located.
|
||||
- `The field <field>` indicates the field name which is causing the offense.
|
||||
- `length of <limit> characters` indicates the character limit allowed for that field.
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
{% callout note %}On import to Bitwarden, the character count of any given field is increased due to encryption, meaning that an 8000-character `note` field in your `.csv` will scale to 10,000+ characters when it comes into contact with Bitwarden, triggering this error. As a rule of thumb, character counts will grow between 30-50% when encrypted.{% endcallout %}
|
||||
- `[1]` identifies the index number where the offending item is located, adjusted to match row numbering in *most* spreadsheet programs.
|
||||
- `[Login]` identifies the Vault item `type` of the offending item.
|
||||
- `"Facebook"` identifies the `name` of the offending item.
|
||||
- `Notes` indicates the field (column) where the character limit is exceeded.
|
||||
- `10000` indicates the character limit allowed for that field (column).
|
||||
|
||||
To solve this issue:
|
||||
{% callout success %}On import to Bitwarden, the character count of any given field is increased due to encryption, meaning that an 8000-character `Notes` field in your `.csv` will scale to 10,000+ characters when it comes into contact with Bitwarden, triggering this error. As a rule of thumb, character counts will grow between 30-50% when encrypted.{% endcallout %}
|
||||
|
||||
1. Open the `.csv` file you're attempting to import in a text editor or spreadsheet program.
|
||||
2. Locate the offending item at `index[X]`. The value of `X` references a `.csv` index number, so depending on the program you use to edit your file it may not map perfectly to a spreadsheet Row or Line number.
|
||||
|
||||
In many cases, you'll need to adjust for `.csv` header rows, which are not counted in many spreadsheet programs. It can also help to use field name (`yyyy`) and perceived character length as context clues.
|
||||
|
||||
{% callout success %}If you're having trouble locating the offending item using the data provided in the error, it may help to focus first on notes as these are frequently the cause of this error.{% endcallout %}
|
||||
3. Remove the offending item from your import file, or reduce the character count. When reducing the character count, remember that limits are placed on **encrypted** counts, not pre-encryption counts. As a rule of thumb, character counts will grow between 30-50% when Bitwarden attempts to encrypt a field on import.
|
||||
If you continue to have trouble locating the offending item using the data provided in the error, it may help to focus first on notes as these are frequently the cause of this error.
|
||||
|
||||
### Maximum Collections Error
|
||||
|
||||
@@ -113,5 +137,5 @@ https://github.com/login,login,password,,,Github,Productivity Tools,0
|
||||
```
|
||||
down to:
|
||||
```
|
||||
https://github.com/login,test,test,,,Github,0
|
||||
https://github.com/login,login,password,,,Github,0
|
||||
```
|
||||
|
||||
@@ -311,6 +311,28 @@ echo '["974053d0-3b33-4b98-886e-fecf5c8dba96"]' | bw encode | \
|
||||
|
||||
The CLI comes with several other commands that you may find useful.
|
||||
|
||||
### send / receive
|
||||
|
||||
The Bitwarden CLI features full support for [Bitwarden Send]({% link _articles/send/about-send.md %}). This section will include some small sample send and receive operations, however it's highly recommended that you **refer to the dedicated article** on [Send from CLI]({% link _articles/send/send-cli.md %}).
|
||||
|
||||
Simple Text Send:
|
||||
|
||||
```
|
||||
bw send -n "My First Send" -d 7 --hidden "The contents of my first text Send."
|
||||
```
|
||||
|
||||
Simple File Send:
|
||||
|
||||
```
|
||||
bw send -n "A Sensitive File" -d 14 -f /Users/my_account/Documents/sensitive_file.pdf
|
||||
```
|
||||
|
||||
Receive a Send:
|
||||
|
||||
```
|
||||
bw receive --password passwordforaccess https://vault.bitwarden.com/#/send/yawoill8rk6VM6zCATXv2A/9WN8wD-hzsDJjfnXLeNc2Q
|
||||
```
|
||||
|
||||
### Confirm
|
||||
|
||||
The `confirm` command allows you to confirm invited members of your organization that have already accepted their invitation.
|
||||
|
||||
18
_articles/miscellaneous/exclude-domains.md
Normal file
18
_articles/miscellaneous/exclude-domains.md
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
layout: article
|
||||
title: Exclude Domains
|
||||
categories: [miscellaneous]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: []
|
||||
---
|
||||
|
||||
Bitwarden Browser Extensions can be configured to exclude (i.e. explicitly not offer to save passwords for) specific domains. When a domain is in the **Excluded Domains** list, Bitwarden won't issue the popup offering to remember an entered password:
|
||||
|
||||
{% image /be-offer.png Browser Extension popup offer %}
|
||||
|
||||
To configure excluded domains, open the {% icon fa-cogs %} **Settings** tab and select the **Excluded Domains** option:
|
||||
|
||||
{% image be-excludeddomains.png Excluded Domains Configuration %}
|
||||
|
||||
*Domain* Exclusion does not register "full" URLs, only the domain component. In the above example, `https://github.com/bitwarden/browser` would resolve to `github.com` when saved, meaning that the Browser Extension would explicitly not offer to save credentials for Github.
|
||||
@@ -26,20 +26,53 @@ When you install Bitwarden on a new device, simply log in to your existing accou
|
||||
|
||||
To manually sync your Vault from a Bitwarden client application:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link active" id="betab" data-bs-toggle="tab" data-target="#be" role="tab" aria-controls="be" aria-selected="true">Browser Extensions</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-bs-toggle="tab" data-target="#mob" role="tab" aria-controls="mob" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-bs-toggle="tab" data-target="#desk" role="tab" aria-controls="desk" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" id="tab" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-bs-toggle="tab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="be" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture be_sync %}
|
||||
### Sync Browser Extensions
|
||||
|
||||
Select the {% icon fa-cogs %} **Settings** tab, select the **Sync** option and select the **Sync Vault Now** button.
|
||||
|
||||
{% endcapture %}
|
||||
{{ be_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="mob" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mob_sync%}
|
||||
### Sync Mobile Apps
|
||||
|
||||
Open the {% icon fa-cogs %} **Settings** tab, tap the **Sync** option and tap **Sync Vault Now**.
|
||||
|
||||
Toggle the **Enable sync on refresh** option to allow your Vault to be synced using a pulldown gesture on the {% icon fa-lock %} **My Vault** tab.
|
||||
|
||||
{% endcapture %}
|
||||
{{ mob_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="desk" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desk_sync%}
|
||||
### Sync Desktop Apps
|
||||
|
||||
Select **File** → **Sync Vault** from the menu bar.
|
||||
|
||||
{% endcapture %}
|
||||
{{ desk_sync | markdownify }}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="clitab">
|
||||
{% capture cli_sync%}
|
||||
### Sync the CLI
|
||||
|
||||
Use the `sync` command to manually sync your Vault:
|
||||
@@ -48,7 +81,11 @@ Use the `sync` command to manually sync your Vault:
|
||||
bw sync
|
||||
```
|
||||
|
||||
For more information, see [The Bitwarden command-line tool (CLI)]({% link _articles/miscellaneous/cli.md %}).
|
||||
For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
{% endcapture %}
|
||||
{{ cli_sync | markdownify }}
|
||||
</div>
|
||||
</div>
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@@ -8,98 +8,49 @@ tags: [organizations, import]
|
||||
order: 08
|
||||
---
|
||||
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your Organization Vault.
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your Organization Vault. You can also use the data import tool to import from one Bitwarden Organization to another, or to import a Bitwarden [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
|
||||
You can also use the data import tool to import from one Bitwarden Vault to another, or to import a backup [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
|
||||
Bitwarden supports a large array of formats for import, including those used by the most popular password management solutions:
|
||||
For a full list of supported import formats, see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/import-faqs/#q-what-file-formats-does-bitwarden-support-for-import), or refer to one of these articles for guidance on the most popular solutions:
|
||||
|
||||
- [Import from LastPass]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- [Import from 1Password]({% link _articles/importing/import-from-1password.md %})
|
||||
- [Import from Firefox]({% link _articles/importing/import-from-firefox.md %})
|
||||
- [Import from Google Chrome]({% link _articles/importing/import-from-chrome.md %})
|
||||
|
||||
For a full list of supported formats, see [Supported Formats](#supported-formats).
|
||||
{% callout info %}
|
||||
**The above listed articles** describe importing to a Personal Bitwarden Vault. While the guidance for exporting from each solution will be appropriate, it's important to know that importing to an Organization is a slightly different procedure and is [documented below](#import-to-your-organization).
|
||||
{% endcallout %}
|
||||
|
||||
## Import to your Organization
|
||||
|
||||
To import data to an Organization Vault:
|
||||
Importing data to Bitwarden **can only be done from the** [**Web Vault**](https://vault.bitwarden.com){:target="\_blank".}. To import data to an Organization Vault:
|
||||
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Organization.
|
||||
2. In your Organization, open the **Tools** tab and select **Import Data** from the left menu.
|
||||
3. Select the format of your file to import from the dropdown menu.
|
||||
4. Select the **Browse...** button and add your file.
|
||||
1. Open your Organization and navigate to the **Tools** tab:
|
||||
|
||||
{% image /importing/org-tools.png Organization Tools %}
|
||||
3. Select **Import Data** from the left-hand Tools menu.
|
||||
3. From the format dropdown, choose a **File Format** (see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/send-faqs/#q-what-file-formats-does-bitwarden-support-for-import)).
|
||||
4. Select the **Choose File** button and add the file to import.
|
||||
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
5. Select the **Import Data** button to complete your import.
|
||||
|
||||
{% callout warning %}
|
||||
Importing data multiple times will create duplicates.
|
||||
{% endcallout %}
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({% link _articles/features/attachments.md %}).
|
||||
|
||||
## Troubleshooting Import Errors
|
||||
## Length-related Import Errors
|
||||
|
||||
If you get the following error:
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
`Ciphers[X].Login: The field **yyyy** exceeds the maximum encrypted value of **zzzz** characters.`
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
An item in your `.CSV` exceeds the size limit allowed for items stored in the Bitwarden Vault. Remove the offending item from your file for import, or reduce its size. You can open the `.CSV` in a text editor or spreadsheet program for easy editing, and locate the offending item at `index[X]` as referenced in the error message.
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
## Supported Formats
|
||||
- `[1]` identifies the index number where the offending item is located, adjusted to match row numbering in *most* spreadsheet programs.
|
||||
- `[Login]` identifies the Vault item `type` of the offending item.
|
||||
- `"Facebook"` identifies the `name` of the offending item.
|
||||
- `Notes` indicates the field (column) where the character limit is exceeded.
|
||||
- `10000` indicates the character limit allowed for that field (column).
|
||||
|
||||
{% callout info %}
|
||||
If your format is not listed below, manually [condition a Bitwarden .csv or .json]({% link _articles/importing/condition-bitwarden-import.md %}).
|
||||
{% endcallout %}
|
||||
{% callout success %}On import to Bitwarden, the character count of any given field is increased due to encryption, meaning that an 8000-character `Notes` field in your `.csv` will scale to 10,000+ characters when it comes into contact with Bitwarden, triggering this error. As a rule of thumb, character counts will grow between 30-50% when encrypted.{% endcallout %}
|
||||
|
||||
The following formats are supported out-of-the-box:
|
||||
|
||||
- [1Password (1pif)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Windows (.sv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- [1Password 6 & 7 Mac (csv)]({% link _articles/importing/import-from-1password.md %})
|
||||
- Ascendo DataVault (csv)
|
||||
- Avast Passwords (csv)
|
||||
- Avira (json)
|
||||
- BlackBerry Password Keeper (csv)
|
||||
- Blur (csv)
|
||||
- [Brave (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Chrome (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Clipperz (html)
|
||||
- Codebook (csv)
|
||||
- Dashlane (json)
|
||||
- Encryptr (csv)
|
||||
- Enpass (csv)
|
||||
- Enpass (json)
|
||||
- [Firefox (csv)]({% link _articles/importing/import-from-firefox.md %})
|
||||
- F-Secure KEY (fsk)
|
||||
- GNOME Passwords and Keys/Seahorse (json)
|
||||
- Kaspersky Password Manager (txt)
|
||||
- KeePass 2 (xml)
|
||||
- KeePassX (csv)
|
||||
- Keeper (csv)
|
||||
- [LastPass (csv)]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- LogMeOnce (csv)
|
||||
- Meldium (csv)
|
||||
- mSecure (csv)
|
||||
- Myki (csv)
|
||||
- [Microsoft Edge (Chromium) (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Opera (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Padlock (csv)
|
||||
- Passbolt (csv)
|
||||
- PassKeep (csv)
|
||||
- Passman (json)
|
||||
- Passpack (csv)
|
||||
- Password Agent (csv)
|
||||
- Password Boss (json)
|
||||
- Password Dragon (xml)
|
||||
- Password Safe (xml)
|
||||
- PasswordWallet (txt)
|
||||
- RememBear (csv)
|
||||
- RoboForm (csv)
|
||||
- SafeInCloud (xml)
|
||||
- SaferPass (csv)
|
||||
- SecureSafe (csv)
|
||||
- SplashID (csv)
|
||||
- Sticky Password (xml)
|
||||
- True Key (csv)
|
||||
- Universal Password Manager (csv)
|
||||
- [Vivaldi (csv)]({% link _articles/importing/import-from-chrome.md %})
|
||||
- Yoti (csv)
|
||||
- Zoho Vault (csv)
|
||||
If you continue to have trouble locating the offending item using the data provided in the error, it may help to focus first on notes as these are frequently the cause of this error.
|
||||
|
||||
@@ -72,7 +72,7 @@ Enabling the **Password Generator** policy will enforce a configurable set of mi
|
||||
{% callout warning %}
|
||||
Existing non-compliant passwords **will not** be changed when this policy is enabled, nor will the items be removed from the Organization. When changing or generating a password after this policy is enabled, configured policy rules will be enforced.
|
||||
|
||||
A banner is displayed to users on the Password Generator screen indicating that a policy will affect their generator settings.
|
||||
A banner is displayed to users on the Password Generator screen to indicate that a policy will affect their generator settings.
|
||||
{% endcallout %}
|
||||
|
||||
### Single Organization
|
||||
@@ -104,3 +104,9 @@ A banner is displayed to users on the Add Item screen indicating that a policy w
|
||||
{% callout info %}
|
||||
Vault Items that were created prior to the implementation of this policy or prior to joining the Organization will remain in the user's personal Vault.
|
||||
{% endcallout %}
|
||||
|
||||
### Disable Send
|
||||
|
||||
Enabling the **Disable Send** policy will prevent non-Owner/non-Admin `?` users from creating or editing a Send using [Bitwarden Send]({% link _articles/send/about-send.md %}). Users subject to this policy will still be able to delete existing Sends that have not yet reached their [Deletion Date]({% link _articles/send/send-lifespan.md %}).
|
||||
|
||||
A banner is displayed to users in the Send view and on opening any existing Send to indicate that a policy is restricting them to only deleting Sends.
|
||||
|
||||
34
_articles/send/about-send.md
Normal file
34
_articles/send/about-send.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: article
|
||||
title: About Send
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, about send, ephemeral sharing]
|
||||
order: 01
|
||||
---
|
||||
|
||||
## What is Send?
|
||||
|
||||
Bitwarden Send is a secure and ephemeral way to transmit sensitive information to **anyone**. Sends can include plaintext or file attachments up to 100 MB. Every Send is assigned a randomly generated and secure link, which can be [shared with anyone]({% link _articles/send/receive-send.md %}) (including those who *do not* have Bitwarden accounts) via text, email, or whatever communication channel you prefer. Every Send is:
|
||||
|
||||
- **End-to-end Encrypted**: Data in a Send is encrypted on creation, and only decrypted when a recipient opens the Send link. The contents of a Send are stored **encrypted** in Bitwarden systems, just like a traditional Vault item. The link generated for each send doesn't contain any data related to the Send's contents, so it's safe to share over intermediary communications services without exposing information to Bitwarden or any used intermediary services.
|
||||
|
||||
- **Dynamically Ephemeral**: Sends are designed for ephemeral sharing, so every [Send that you create]({% link _articles/send/create-send.md %}) will have a specified [lifespan]({% link _articles/send/send-lifespan.md %}) (*max 30 days*) that can be configured using pre-set options or a custom timestamp for down-to-the-minute specification. When its deletion date is reached, the Send and its contents will be completely purged from Bitwarden systems. Using additional options like [Expiration Date]({{site.baseurl}}/article/send-lifespan/#expiration-date) and [Maximum Access Count]({{site.baseurl}}/article/send-lifespan/#maximum-access-count), you can ensure that access to recipients is terminated according to your needs.
|
||||
|
||||
- **Customizably Private**: Protect the contents of your Send by optionally [configuring a password]({{site.baseurl}}/article/send-privacy/#send-passwords) for access so that no unintended recipients can see the contained information. For text Sends, you can also optionally [require users to toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) to prevent exposure to unintentional onlookers.
|
||||
|
||||
## The Send View
|
||||
|
||||
Sends are created, edited, managed, and deleted from the **Send** view in any Bitwarden application. The **Send** view can be accessed from the global application navigation, for example in the Web Vault:
|
||||
|
||||
{% image /send/send-webvault.png Send in the Web Vault %}
|
||||
|
||||
## Using Send
|
||||
|
||||
Using Bitwarden Send is a simple two-step process:
|
||||
|
||||
1. [Create your Send]({% link _articles/send/create-send.md %}), setting whichever [lifespan options]({% link _articles/send/send-lifespan.md %}) and [privacy options]({% link _articles/send/send-privacy.md %}) are required to fit your sharing needs.
|
||||
2. Share the Send link with the [intended recipients]({% link _articles/send/receive-send.md %}), using whatever communication channel you prefer.
|
||||
|
||||
As the Sender, we recommend that you keep track of your Send's [configured lifespan]({% link _articles/send/send-lifespan.md %}). To make that as easy as possible, Sends in your Send view will display [a set of status icons]({{site.baseurl}}/article/send-faqs/#q-what-do-the-icons-next-to-my-sends-indicate) whenever a lifespan event (for example, expiration) has occurred.
|
||||
235
_articles/send/create-send.md
Normal file
235
_articles/send/create-send.md
Normal file
@@ -0,0 +1,235 @@
|
||||
---
|
||||
layout: article
|
||||
title: Create a Send
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, create a send, how to, ephemeral sharing]
|
||||
order: 02
|
||||
---
|
||||
|
||||
Creation of file Sends is available for Premium users, including members of a Paid Organization (Families, Teams, or Enterprise). Free users may still create text Sends.
|
||||
|
||||
Sends can be created and edited from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} or any Bitwarden client application. Choose the Bitwarden application you want to Send from to get started:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab">
|
||||
{% capture web_vault %}
|
||||
### Send from the Web Vault
|
||||
|
||||
Complete the following steps to create a new Send from the Bitwarden [Web Vault](https://vault.bitwarden.com){:target="\_blank"}:
|
||||
|
||||
1. Select **Send** from the top navigation bar.
|
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date). Like the **My Vault** view, you can filter your Sends by selecting one of the available **Types**.
|
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Create New Send** button:
|
||||
|
||||
{% image /send/send-create-webvault.png Send View in the Web Vault %}
|
||||
3. On the **Create New Send** dialog, specify the following to create the contents of your Send:
|
||||
|
||||
- **What type of Send is this?**: Specify whether this Send will be **Text** or a **File**:
|
||||
|
||||
|**Text**|Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) when they open a Send.|
|
||||
|**File**|Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)|
|
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send.
|
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send.
|
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired:
|
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.|
|
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.|
|
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.|
|
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.|
|
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.|
|
||||
**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.|
|
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %}
|
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish.
|
||||
|
||||
Once your Send is created, use the hover-over {% icon fa-cog %} gear dropdown and select the {% icon fa-copy %} **Copy Send link** button to copy the generated link to your clipboard:
|
||||
|
||||
{% image /send/send-from-webvault.png Copy a Send link %}
|
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use.
|
||||
|
||||
{% endcapture %}
|
||||
{{ web_vault | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
### Send from a Browser Extension
|
||||
|
||||
Complete the following steps to create a new Send from a Bitwarden Browser Extension:
|
||||
|
||||
1. Select the {% icon fa-paper-plane %} **Send** tab located at the bottom of your Browser Extension.
|
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types**.
|
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Add** icon:
|
||||
|
||||
{% image /send/send-browserext.png Send View in a Browser Extension %}
|
||||
|
||||
3. On the **Add Send** view, specify the following to create the contents of your Send:
|
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send.
|
||||
- **Type**: Specify whether this Send will be **Text** or a **File**:
|
||||
|
||||
|**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) when they open a Send.|
|
||||
|**File** | Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)<br><br>If you're using **Firefox or Safari**, you'll need to popout ({% icon fa-external-link fa-rotate-270 %}) the Browser Extension in order to browse for the file to send.|
|
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send.
|
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired:
|
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.|
|
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.|
|
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.|
|
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.|
|
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.|
|
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.|
|
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %}
|
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish.
|
||||
|
||||
Once your Send is created, select the {% icon fa-copy %} **Copy Link** icon to copy the generated link to your clipboard:
|
||||
|
||||
{% image /send/send-be-share.png Copy a Send link %}
|
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use.
|
||||
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
### Send from a Desktop App
|
||||
|
||||
Complete the following steps to create a new Send from a Bitwarden Desktop App:
|
||||
|
||||
1. Select the {% icon fa-paper-plane %} **Send** tab located at the bottom of the left-most column in your Desktop App.
|
||||
|
||||
The center column will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types** from the left-most column.
|
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Add** icon in at the bottom of the center column.
|
||||
|
||||
{% image /send/send-desktop-add.png Send view in a Desktop App %}
|
||||
3. In the right-most column, specify the following to create the contents of your Send:
|
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send.
|
||||
- **Type**: Specify whether this Send will be **Text** or a **File**:
|
||||
|
||||
| **Text** | Type or paste the desired text into the input box. Toggle the **When accessing the send, hide text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.|
|
||||
| **File** | Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)|
|
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send.
|
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired:
|
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.|
|
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.|
|
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.|
|
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.|
|
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.|
|
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.|
|
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %}
|
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish.
|
||||
|
||||
Once your Send is created, select the {% icon fa-copy %} **Copy Link** button to copy the generated link to your clipboard:
|
||||
|
||||
{% image /send/send-desktop-share.png Copy a Send link %}
|
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use.
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
### Send from a Mobile App
|
||||
|
||||
Complete the following steps to create a new Send from Bitwarden Mobile App:
|
||||
|
||||
1. Tap the {% icon fa-paper-plane %} **Send** tab located at the bottom of your screen.
|
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by tapping one of the available **Types**.
|
||||
2. To start creating a new Send, tap the {% icon fa-plus %} **Add** icon:
|
||||
|
||||
{% image /send/send-mobile.png Send View on iOS and Android%}
|
||||
|
||||
3. On the **Add Send** view, specify the following to create the contents of your Send:
|
||||
|
||||
- **Type**: Specify whether this Send will be **Text** or a **File**:
|
||||
|
||||
|**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.|
|
||||
|**File** | Tap the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)|
|
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send.
|
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise tap **Save** to finish creating your Send.
|
||||
|
||||
4. Tap the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired:
|
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.|
|
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.|
|
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.|
|
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.|
|
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.|
|
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.|
|
||||
|
||||
{% callout success%}Toggling the **Share upon save** option before you tap **Save** will open the share menu on your device so you can quickly share your Send link.{% endcallout %}
|
||||
|
||||
Once you're happy with the configuration of your Send, tap the **Save** button to finish.
|
||||
|
||||
Once your Send is created, tap the menu icon ( {% icon fa-ellipsis-v %} or {% icon fa-ellipsis-h %} ) and tap the **Share Link** option:
|
||||
|
||||
{% image /send/send-share-mob.png Copy a Send link %}
|
||||
|
||||
Share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use.
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab">
|
||||
{% capture cli_info %}
|
||||
### Send from the CLI
|
||||
|
||||
The following are sample commands to help you get started using Send from the CLI.
|
||||
|
||||
To create a simple text Send with a [deletion date]({{site.baseurl}}/articles/send-lifespan/#deletion-date) set to 14 days from creation:
|
||||
|
||||
```
|
||||
bw send -n "My Text Send" -d 14 "My first secret message."
|
||||
```
|
||||
|
||||
To create a simple file Send with a [deletion date]({{site.baseurl}}/articles/send-lifespan/#deletion-date) set to 14 days from creation:
|
||||
|
||||
```
|
||||
bw send -n "My File Send" - d 14 -f /Users/myaccount/Documents/my_file.pdf
|
||||
```
|
||||
|
||||
The Bitwarden CLI is a fully-featured and powerful tool. We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article to learn more.
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
27
_articles/send/receive-send.md
Normal file
27
_articles/send/receive-send.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
layout: article
|
||||
title: Receive a Send
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, receive, receive a send]
|
||||
order: 03
|
||||
---
|
||||
|
||||
Unlike traditional Bitwarden Vault items, a Send can be received and opened by anyone with the Send link (including those who *do not* have Bitwarden accounts). Send links are randomly generated, and will look something like the following:
|
||||
|
||||
- `https://vault.bitwarden.com/#/send/yawoill8rk6VM6zCATXv2A/9WN8wD-hzsDJjfnXLeNc2Q`
|
||||
- `https://your.selfhosted.domain.com/#/send/yawoill8rk6VM6zCATXv2A/9WN8wD-hzsDJjfnXLeNc2Q`
|
||||
|
||||
These links can be opened in any modern web browser, and will open a simple no-navigation web page, for example:
|
||||
|
||||
{% image /send/received-send.png A received Send%}
|
||||
|
||||
Depending on the [options configured]({% link _articles/send/create-send.md %}) by the Sender, the recipient of a Send may be required to:
|
||||
|
||||
- Enter a Password to access the contents of the Send.
|
||||
- Manually toggle visibility on a hidden-text Send.
|
||||
|
||||
When a Send has [been deleted, expired, or disabled]({% link _articles/send/send-lifespan.md %}), recipients who attempt to use the generated Send link will be shown a screen that reports the Send does not exist or is no longer available:
|
||||
|
||||
{% image /send/send-unavailable.png A deleted, expired, or disabled Send %}
|
||||
195
_articles/send/send-cli.md
Normal file
195
_articles/send/send-cli.md
Normal file
@@ -0,0 +1,195 @@
|
||||
---
|
||||
layout: article
|
||||
title: Send from CLI
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, cli]
|
||||
order: 06
|
||||
---
|
||||
|
||||
Bitwarden Send is available as a set of fully-featured CLI commands. This article documents the breadth of `bw send` commands, however Send **is not a separate tool** from the Bitwarden Command-line Interface (CLI). Therefore, many of the commands, options, and concepts in the [CLI documentation]({% link _articles/miscellaneous/cli.md %}) are relevant here.
|
||||
|
||||
{% image /send/send-cli.png Send's --help text %}
|
||||
|
||||
## send
|
||||
|
||||
The `send` command is the master command used to access all Send-related subcommands:
|
||||
|
||||
```
|
||||
bw send [options] [command] <data>
|
||||
```
|
||||
|
||||
The `send` command can **also** be used as a shortcut to quickly `create` a Send, for example:
|
||||
|
||||
```
|
||||
bw send "Fastest Send in the West."
|
||||
```
|
||||
|
||||
will create a text Send object with the contents `Fastest Send in the West.` and output the Send link. Or, for example:
|
||||
|
||||
```
|
||||
bw send -f <path/to/file.ext>
|
||||
```
|
||||
|
||||
will create a file Send object with the specified file at the specified `path` and output the Send link.
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `-n <name>` or `--name <name>` to specify a name for the Send. If none is specified, name will default to the `id` for text Sends and file name for file Sends. For multi-word names, use quotations `"<name>"`.
|
||||
- Use `-d <days>` or `--deleteInDays <days>` to specify a [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date) for the Send (defaults to 7 days if unspecified).
|
||||
- Use `--hidden` to specify that a text Send require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text).
|
||||
- Use `--notes <notes>` to add private notes to the Send. For multi-word notes, use quotations `"<notes>"`.
|
||||
- Use `--fullObject` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON).
|
||||
|
||||
**Full Example:**
|
||||
|
||||
```
|
||||
bw send -n "My First Send" -d 7 --hidden "The contents of my first Send."
|
||||
```
|
||||
|
||||
### create
|
||||
|
||||
The `create` command creates a Send. `create` allows more advanced configuration than using only `bw send` and takes encoded JSON for its argument:
|
||||
|
||||
```
|
||||
bw send create [options] <encodedJson>
|
||||
```
|
||||
|
||||
A typical workflow might look something like:
|
||||
|
||||
1. Use the `template` command (see [details](#template)) to output the appropriate JSON template for your Send type.
|
||||
2. Use a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} to manipulate the outputted template as required.
|
||||
3. Use the `encode` command (see [details]({{site.baseurl}}/article/cli/#encode)) to encode the manipulated JSON.
|
||||
4. Use the `create` command to create a Send from the encoded JSON.
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
bw send template send.text | jq '.name="My First Send" | .text.text="Secrets I want to share."' | bw encode | bw send create
|
||||
```
|
||||
or
|
||||
```
|
||||
bw send template send.text | jq ".name=\"My First Send\" | .text.text=\"Secrets I want to share.\" | .password=\"mypassword\" | .deletionDate=\"$(date -uv+14d + "%Y-%m-%dT%H:%M:%SZ")\"" | bw encode | bw send create
|
||||
```
|
||||
|
||||
{% callout success %}
|
||||
Notice in the 2nd example that the jq invokation must be wrapped in double quotes (`" "`) and use escapes (`\`) for each filter due to a nested `date` variable that configures a `.deletionDate` in the Send.
|
||||
{% endcallout %}
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `--file <path>` to specify the file to Send (this can also be specified in encoded JSON).
|
||||
- Use `--text <text>` to specify the text to Send (this can also be specified in encoded JSON).
|
||||
- Use `--hidden` to specify that a text Send require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text).
|
||||
- Use `--password <password>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords).
|
||||
- Use `--fullObject` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON).
|
||||
|
||||
### get
|
||||
|
||||
The `get` command will retrieve a Send owned by you and output it as a JSON object. `get` takes an exact `id` value or any string for its argument. If you use a string, `get` will search your Sends for one with a value that matches:
|
||||
|
||||
```
|
||||
bw send get [options] <id / string>
|
||||
```
|
||||
|
||||
If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `--text` to output only the text contents of a text Send.
|
||||
- Use `--file` to output only the file of a file Send. Pair `--file` with `--output` to specify a directory, or with `--raw` to output to stdout.
|
||||
- Use `--output <output>` to specify the output directory for the `--file` option.
|
||||
|
||||
### edit
|
||||
|
||||
The `edit` command edits an existing Send object. `edit` takes encoded JSON for its argument:
|
||||
|
||||
```
|
||||
bw send edit <encodedJson>
|
||||
```
|
||||
|
||||
A typical workflow might look something like:
|
||||
|
||||
1. Use the `get` command (see [details](#get)) to retrieve the desired Send according to its `<id>`.
|
||||
2. Use a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} to manipulate the retrieved Send as required.
|
||||
3. Use the `encode` command (see [details]({{site.baseurl}}/article/cli/#encode)) to encode the manipulated JSON.
|
||||
4. Use the `edit` command to write the edits to the Send.
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
bw send get <id> | jq '.name="New Name" | .password=null' | bw encode | bw send edit
|
||||
```
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `--itemid <itemid>` to overwrite the id value provided of the Send with a new one.
|
||||
|
||||
{% callout note %}
|
||||
You can't `edit` a file Send's file. To do this, you'll need to delete the Send and re-create it with the appropriate file.
|
||||
{% endcallout %}
|
||||
|
||||
### list
|
||||
|
||||
The `list` command will list all Sends owned by you and output them as JSON:
|
||||
|
||||
```
|
||||
bw send list [options]
|
||||
```
|
||||
|
||||
If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}).
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `--pretty` to format the JSON the output.
|
||||
- Pipe stdout to a file using the `>` operator, for example:
|
||||
|
||||
```
|
||||
bw send list --pretty > /Users/myaccount/Documents/pretty_list_of_sends.json
|
||||
```
|
||||
|
||||
### delete
|
||||
|
||||
The `delete` command will delete a Send owned by you. `delete` takes only an exact `id` value for its argument.
|
||||
|
||||
```
|
||||
bw send delete <id>
|
||||
```
|
||||
|
||||
{% callout success %}
|
||||
If you don't know the exact `id` of the Send you want to delete, use `bw send get <search term>` to find it.
|
||||
{% endcallout %}
|
||||
|
||||
### template
|
||||
|
||||
The `template` command returns the expected JSON formatting for a Send object. `template` takes an `<object>` specification for its argument, either `send.text` or `send.file`.
|
||||
|
||||
```
|
||||
bw send template <object>
|
||||
```
|
||||
|
||||
While you *can* use `template` to output the format to your screen, the most common use-case is to pipe the output into a `bw send create` operation, using a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} and `bw encode` to manipulate the values retrieved from the template, for example:
|
||||
|
||||
```
|
||||
bw send template send.text | jq '.name="My First Send" | .text.text="Secrets I want to share."' | bw encode | bw send create
|
||||
```
|
||||
|
||||
## receive
|
||||
|
||||
The `receive` command accesses a Send. `receive` takes a Send `<url>` for its argument:
|
||||
|
||||
```
|
||||
bw send receive [options] <url>
|
||||
```
|
||||
|
||||
- For text Sends, `receive` will return the text contents of the Send to stdout.
|
||||
- For file Sends, `receive` will download the file to the current working directory.
|
||||
|
||||
**Options:**
|
||||
|
||||
- Use `--password <password>` to provide the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a string.
|
||||
- Use `--passwordenv <passwordenv>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a stored environment variable.
|
||||
- Use `--passwordfile <passwordfile>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a file with the password as its first line.
|
||||
- Use `--obj` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON).
|
||||
- Use `--ouput <output>` to specify the output directory for the contents of a file Send.
|
||||
19
_articles/send/send-hosting.md
Normal file
19
_articles/send/send-hosting.md
Normal file
@@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: article
|
||||
title: Self-hosting Send
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 07
|
||||
---
|
||||
|
||||
Once you [update your instance]({% link _articles/hosting/updating-on-premise.md %}), most implementations will be already setup to begin [using Send]({% link _articles/send/create-send.md %}). An exception to this is if you're using a non-default **mapped volume for attachment storage**.
|
||||
|
||||
The files attached to File Sends are stored in a `send` subdirectory of the existing attachments volume (i.e. `./bwdata/core/attachments/send`). This is dictated by the `globalSettings__send__baseDirectory=` environment variable, which has the following default configuration in `global.override.env`:
|
||||
|
||||
```
|
||||
globalSettings__send__baseDirectory=/etc/bitwarden/core/attachments/send
|
||||
```
|
||||
|
||||
If you want to store the files attached to File Sends in your non-default attachments volume, you'll need to point `globalSettings__send__baseDirectory=` to the new volume. For more information, see [Configure Environment Variables](#).
|
||||
211
_articles/send/send-lifespan.md
Normal file
211
_articles/send/send-lifespan.md
Normal file
@@ -0,0 +1,211 @@
|
||||
---
|
||||
layout: article
|
||||
title: Send Lifespan
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, ephemeral sharing, deletion, expiration, access count]
|
||||
order: 04
|
||||
---
|
||||
|
||||
Unlike traditional Bitwarden Vault items and File Attachments, Sends are ephemeral and have a **default lifespan of 7 days**. The lifespan of a Send is entirely configurable using the [Deletion Date](#deletion-date) option, each having a maximum allowed lifespan of 30 days. When a Send has reached its Deletion Date, it will be purged from Bitwarden systems and inaccessible to both its Sender and recipients.
|
||||
|
||||
**Optionally**, you can configure additional limitations on recipient access using the [Expiration Date](#expiration-date) and/or [Maximum Access Count](#maximum-access-count) options.
|
||||
|
||||
You can also manually [disable or delete](#manually-disable-or-delete) a Send at any time.
|
||||
|
||||
## Deletion Date
|
||||
|
||||
By default, a Send will have a Deletion Date set to 7 days from creation. Using the **Deletion Date** option, you may change this to a range of pre-specified options (e.g. *1 hour*, *1 day*, *30 days*) or specify a **Custom** timestamp using the date picker (or in the text input in the format `MM/DD/YYYY HH:MM AM/PM`).
|
||||
|
||||
Deletion Date has a **maximum allowed value of 30 days from creation**.
|
||||
|
||||
### Deletion Behavior
|
||||
|
||||
When a Send reaches its configured Deletion Date:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-trash %} **Pending Deletion** icon will appear next to the Send. The Send will pend deletion for a few minutes, after which it will be permanently deleted from Bitwarden systems and from the Sender's Send view.
|
||||
|
||||
{% callout note %}There is no "soft delete" or Trash Can for Sends, meaning that once the pending deletion window has closed you will not be able to access the contents of a Send.{% endcallout %}
|
||||
|
||||
## Expiration Date
|
||||
|
||||
By default, Expiration Date will be set to Never. Using the **Expiration Date** option, you may change this to a range of pre-specified options (e.g. *1 hour*, *1 day*, *7 days*) or specify a **Custom** timestamp using the date picker (or in the text input in the format `MM/DD/YYYY HH:MM AM/PM`).
|
||||
|
||||
### Expiration Behavior
|
||||
|
||||
When a Send reaches its specified Expiration Date:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, an {% icon fa-clock-o %} **Expired** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
## Maximum Access Count
|
||||
|
||||
For all Sends, a **Current Access Count** ticker will track the number of times the Send link has been accessed:
|
||||
|
||||
{% image /send/send-access-ticker.png Current Access Count ticker %}
|
||||
|
||||
For any Send, you may specify a **Maximum Access Count** that is a positive integer.
|
||||
|
||||
### Maximum Access Count Behavior
|
||||
|
||||
When a Send reaches its specified Maximum Access Count:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-ban %} **Max access count reached** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
{% callout success %}
|
||||
The **Current Access Count** ticker counts:
|
||||
- For text Sends, the number of times the link has been accessed.
|
||||
- For file Sends, the number of times the contents are downloaded.
|
||||
{% endcallout %}
|
||||
|
||||
## Manually Disable or Delete
|
||||
|
||||
Manually disable or delete a Send from any Bitwarden application:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab">
|
||||
{% capture web_vault %}
|
||||
|
||||
#### Disable from the Web Vault
|
||||
|
||||
To disable a Send from the Web Vault, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send.
|
||||
|
||||
{% image /send/send-disable-wv.png Disable from the Web Vault %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
#### Delete from the Web Vault
|
||||
|
||||
To delete a Send from the Web Vault, use the hover-over {% icon fa-cog %} gear dropdown to select the {% icon fa-trash %} **Delete** button:
|
||||
|
||||
{% image /send/send-delete.png Delete from the Web Vault %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ web_vault | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab">
|
||||
{% capture browser_extension %}
|
||||
|
||||
#### Disable from Browser Extensions
|
||||
|
||||
To disable a Send from a Browser Extension, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send.
|
||||
|
||||
{% image /send/send-disable-be.png Disable from a Browser Extension %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
#### Delete from Browser Extensions
|
||||
|
||||
To delete a Send from a Browser Extension, select the {% icon fa-trash %} **Trash** icon next to the Send you want to delete:
|
||||
|
||||
{% image /send/send-delete-be.png Delete from a Browser Extension %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab">
|
||||
{% capture desktop_info %}
|
||||
|
||||
#### Disable from Desktop Apps
|
||||
|
||||
To disable a Send from a Desktop App, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send.
|
||||
|
||||
{% image /send/send-desktop-disable.png Disable from a Desktop App%}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
#### Delete from Desktop Apps
|
||||
|
||||
To delete a Send from a Desktop App, open the **Edit Send** view and select the {% icon fa-trash %} **Delete** button:
|
||||
|
||||
{% image /send/send-desktop-delete.png Delete from a Desktop App %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab">
|
||||
{% capture mobile_info %}
|
||||
|
||||
#### Disable from Mobile Apps
|
||||
|
||||
To disable a Send from a Mobile App, open the **Edit Send** view and toggle the **Disable this Send so that no one can access it** option. You can toggle this option off at any time to re-enable access to the Send.
|
||||
|
||||
{% image /send/send-disable-mobile.png Disable from a Mobile App %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available.
|
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached.
|
||||
|
||||
#### Delete from Mobile Apps
|
||||
|
||||
To delete a Send from a Mobile App, tap the menu icon ( {% icon fa-ellipsis-v %} or {% icon fa-ellipsis-h %} ) and tap the **Delete** option:
|
||||
|
||||
{% image /send/send-delete-mob.png Delete from a Mobile App %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
</div>
|
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab">
|
||||
{% capture cli_info %}
|
||||
|
||||
#### Disable from the CLI
|
||||
|
||||
To disable a Send from the CLI, you'll need to use the `edit` command to change the `"disabled":false` key-value pair to `"disabled":true`, for example:
|
||||
|
||||
```
|
||||
bw send get <id> | jq '.disabled=false' | bw encode | bw send edit
|
||||
```
|
||||
|
||||
We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI.
|
||||
|
||||
#### Delete from the CLI
|
||||
|
||||
To delete a Send from the CLI, use the `delete` command with the Send's exact unique `id` as an argument:
|
||||
|
||||
```
|
||||
bw send delete <id>
|
||||
```
|
||||
|
||||
We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI.
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
</div>
|
||||
</div>
|
||||
36
_articles/send/send-privacy.md
Normal file
36
_articles/send/send-privacy.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
layout: article
|
||||
title: Send Privacy
|
||||
categories: [send]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [bitwarden send, send, passwords, hidden text]
|
||||
order: 05
|
||||
---
|
||||
Protect the contents of your Send by optionally configuring a [password for access](#passwords) so that no unintended recipients can see the contained information. For text Sends, you can also optionally require recipients to [toggle visibility](#hide-text) to prevent exposure to unintentional onlookers.
|
||||
|
||||
The **Password** and **Hide Text** options are configurable from the Create New Send view, or from the Edit Send views at any time prior to the Send's [deletion]({{site.baseurl}}/article/send-lifespan/#deletion-behavior).
|
||||
|
||||
## Send Passwords
|
||||
|
||||
For any Send, you may configure a password that recipients will be required to enter in order to access its contents. Password-protecting a Send is a good way to ensure the contents of a Send aren't exposed to unintended recipients:
|
||||
|
||||
{% image /send/send-pw-protected.png Receiving a password-protected Send%}
|
||||
|
||||
Once you password-protect a Send, you won't be able to view the configured password again, however you can [change](#change-send-passwords) or [remove](#remove-send-password) at any time:
|
||||
|
||||
### Change Send Passwords
|
||||
|
||||
You can change a Send's password at any time from the **Edit Send** view. Changing a Send's password **will not** require you to enter the previous password. When changing a Send's password, the **Password** field will change to **New Password**:
|
||||
|
||||
{% image /send/send-new-pw.png %}
|
||||
|
||||
### Remove Send Passwords
|
||||
|
||||
You can remove a Send's password at any time using the {% icon fa-undo %} **Remove Password** menu option. Removing a Send's password **will not** require you to enter the previous password.
|
||||
|
||||
## Hide Text
|
||||
|
||||
For text Sends, toggle the **When accessing the Send, hide the text by default** option to require recipients to {% icon fa-eye %} **Toggle Visibility** in order to see its contents. Hiding the text on a Send is a good way to ensure the contents of a Send aren't exposed to unintentional onlookers:
|
||||
|
||||
{% image /send/send-hidden-text.png Receiving a hidden-text Send%}
|
||||
@@ -17,8 +17,8 @@ Any FIDO U2F certified device can be used, including YubiKeys, SoloKeys, Google
|
||||
|
||||
Supported applications:
|
||||
|
||||
- Web Vault on a computer with a U2F-enabled Browser (Chrome, Opera, Vivaldi, or [Firefox with FIDO U2F enabled](https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/){:target="_blank"}).
|
||||
- Browser Extensions for a U2F-enabled Browser (Chrome, Opera, Vivaldi, or [Firefox with FIDO U2F enabled](https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/){:target="_blank"}).
|
||||
- Web Vault on a computer with a U2F-enabled Browser (Chrome, Opera, Vivaldi, Edge, or [Firefox with FIDO U2F enabled](https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/){:target="_blank"}).
|
||||
- Browser Extensions for a U2F-enabled Browser (Chrome, Opera, Vivaldi, Edge, or [Firefox with FIDO U2F enabled](https://www.yubico.com/2017/11/how-to-navigate-fido-u2f-in-firefox-quantum/){:target="_blank"}).
|
||||
{% endcallout %}
|
||||
|
||||
## Setup FIDO U2F
|
||||
|
||||
5
_categories/send.md
Normal file
5
_categories/send.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
layout: category
|
||||
title: Bitwarden Send
|
||||
featured: true
|
||||
---
|
||||
@@ -28,6 +28,7 @@ collections:
|
||||
order:
|
||||
- getting-started.md
|
||||
- account-management.md
|
||||
- send.md
|
||||
- import-export.md
|
||||
- two-step-login.md
|
||||
- hosting.md
|
||||
@@ -36,6 +37,7 @@ collections:
|
||||
- login-with-sso.md
|
||||
- security.md
|
||||
- plans-and-pricing.md
|
||||
- miscellaneous.md
|
||||
articles:
|
||||
output: true
|
||||
permalink: /article/:name/
|
||||
|
||||
BIN
images/be-excludeddomains.png
Normal file
BIN
images/be-excludeddomains.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
BIN
images/be-offer.png
Normal file
BIN
images/be-offer.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
BIN
images/biometrics/be-bio-unlock.png
Normal file
BIN
images/biometrics/be-bio-unlock.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
BIN
images/importing/ciphererror_2021.png
Normal file
BIN
images/importing/ciphererror_2021.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
BIN
images/importing/org-tools.png
Normal file
BIN
images/importing/org-tools.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 71 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 76 KiB |
BIN
images/send/expired-send.png
Normal file
BIN
images/send/expired-send.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
images/send/received-send.png
Normal file
BIN
images/send/received-send.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 146 KiB |
BIN
images/send/send-access-ticker.png
Normal file
BIN
images/send/send-access-ticker.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
images/send/send-be-share.png
Normal file
BIN
images/send/send-be-share.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
images/send/send-browserext.png
Normal file
BIN
images/send/send-browserext.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 185 KiB |
BIN
images/send/send-cli.png
Normal file
BIN
images/send/send-cli.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 105 KiB |
BIN
images/send/send-create-webvault.png
Normal file
BIN
images/send/send-create-webvault.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
BIN
images/send/send-delete-be.png
Normal file
BIN
images/send/send-delete-be.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
images/send/send-delete-mob.png
Normal file
BIN
images/send/send-delete-mob.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 124 KiB |
BIN
images/send/send-delete.png
Normal file
BIN
images/send/send-delete.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
BIN
images/send/send-desktop-add.png
Normal file
BIN
images/send/send-desktop-add.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 145 KiB |
BIN
images/send/send-desktop-delete.png
Normal file
BIN
images/send/send-desktop-delete.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 145 KiB |
BIN
images/send/send-desktop-disable.png
Normal file
BIN
images/send/send-desktop-disable.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
BIN
images/send/send-desktop-share.png
Normal file
BIN
images/send/send-desktop-share.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 148 KiB |
BIN
images/send/send-desktop.png
Normal file
BIN
images/send/send-desktop.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 144 KiB |
BIN
images/send/send-disable-be.png
Normal file
BIN
images/send/send-disable-be.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
images/send/send-disable-mobile.png
Normal file
BIN
images/send/send-disable-mobile.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 164 KiB |
BIN
images/send/send-disable-wv.png
Normal file
BIN
images/send/send-disable-wv.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
images/send/send-ff-popout.png
Normal file
BIN
images/send/send-ff-popout.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
BIN
images/send/send-file.png
Normal file
BIN
images/send/send-file.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
BIN
images/send/send-from-webvault.png
Normal file
BIN
images/send/send-from-webvault.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
BIN
images/send/send-hidden-text.png
Normal file
BIN
images/send/send-hidden-text.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
BIN
images/send/send-in-browser.png
Normal file
BIN
images/send/send-in-browser.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
BIN
images/send/send-iphone.png
Normal file
BIN
images/send/send-iphone.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 171 KiB |
BIN
images/send/send-mobile.png
Normal file
BIN
images/send/send-mobile.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
BIN
images/send/send-new-pw.png
Normal file
BIN
images/send/send-new-pw.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
BIN
images/send/send-pw-protected.png
Normal file
BIN
images/send/send-pw-protected.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
images/send/send-share-mob.png
Normal file
BIN
images/send/send-share-mob.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 123 KiB |
BIN
images/send/send-unavailable.png
Normal file
BIN
images/send/send-unavailable.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 131 KiB |
BIN
images/send/send-variety.png
Normal file
BIN
images/send/send-variety.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
images/send/send-webvault.png
Normal file
BIN
images/send/send-webvault.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Reference in New Issue
Block a user