bitwarden/help
1
0
Fork 0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Code Issues Releases Wiki Activity

update articles for icons, u2f, and yubikeys

Browse Source
This commit is contained in:
Kyle Spearrin
2018-06-19 18:19:50 -04:00
parent f8c775c5fa
commit 3aeb15463a
3 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
_articles/account/setup-two-step-login-u2f.md
View File

@@ -14,8 +14,8 @@ Due to platform limitations, FIDO U2F cannot be used on all Bitwarden applicatio
Supported platforms:
- Web vault on a desktop/laptop with a U2F enabled browser (Chrome, Opera, Vivaldi, Brave, or [Firefox with addon](https://addons.mozilla.org/en-US/firefox/addon/u2f-support-add-on/){:target="_blank"}).
- Browser extensions on Chrome, Opera, Vivaldi, or Brave.
- Web vault on a desktop/laptop 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 on 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"}.
{% endnote %}
## Enable Two-step Login with FIDO U2F

7
_articles/account/setup-two-step-login-yubikey.md
View File

@@ -15,8 +15,11 @@ Due to platform limitations, YubiKeys cannot be used on all Bitwarden applicatio
Supported platforms:
- Web vault on a device with a USB port that can accept your YubiKey.
- Browser extensions.
- Android on a device with [NFC capabilities](https://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices){:target="_blank"}. Read more [here](https://forum.yubico.com/viewtopic.php?f=26&t=1302){:target="_blank"}.
- Browser extensions on a device with a USB port that can accept your YubiKey.
- Desktop app on a device with a USB port that can accept your YubiKey.
- CLI on a device with a USB port that can accept your YubiKey.
- Android on a device with [NFC capabilities](https://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices){:target="_blank"} or a USB port that can accept your YubiKey. Read more [here](https://forum.yubico.com/viewtopic1c5f.html?f=26&t=1302){:target="_blank"}.
- iOS on a device with [NFC capabilities](https://en.wikipedia.org/wiki/List_of_NFC-enabled_mobile_devices){:target="_blank"}.
{% endnote %}
## Enable Two-step Login with YubiKey

5
_articles/miscellaneous/website-icons.md
View File

@@ -13,13 +13,13 @@ tags: [icons, website icons, privacy]
When Bitwarden displays a login item associated with a website in your Bitwarden vault it attempts to accompany it with a "website icon". This "website icons" feature allows you to easily identify particular logins in your vault by a recognizable icon. This is usually represented by a logo or brand image of that website. The Bitwarden icons server provides the delivery endpoint for these website icons.
If you are using the "website icons" feature on a device, Bitwarden will issue requests to `icons.bitwarden.com` for each item of type "Login" in your vault that has a URI that resembles a website (ex. `google.com` or `https://google.com`, but not `google` or `http://localhost`). The icons server is fronted with a CDN that caches the icons on Cloudflare's edge nodes all around the world. Subsequent requests to the same icon will likely hit CDN caches instead of the icons server directly. Your requests may never actually hit Bitwarden's icons server because another Bitwarden user with the same website in their vault requested the icon before you.
If you are using the "website icons" feature on a device, Bitwarden will issue requests to `icons.bitwarden.net` for each item of type "Login" in your vault that has a URI that resembles a website (ex. `google.com` or `https://google.com`, but not `google` or `http://localhost`). The icons server is fronted with a CDN that caches the icons on Cloudflare's edge nodes all around the world. Subsequent requests to the same icon will likely hit CDN caches instead of the icons server directly. Your requests may never actually hit Bitwarden's icons server because another Bitwarden user with the same website in their vault requested the icon before you.
## Privacy concerns
Because a request for an icon image contains the hostname of the website stored in your vault, it is important to understand that this feature will "leak" otherwise cryptographically protected information to Bitwarden servers and/or CDN endpoints. An example of a icon request looks like the following:
`https://icons.bitwarden.com/google.com/icon.png`
`https://icons.bitwarden.net/google.com/icon.png`
**The icons server endpoints do not log or collection any information regarding icon image requests.** However, this is something you would have to take our word for since we have no way to demonstrate this publicly other than reviewing our [open source codebase](https://github.com/bitwarden).
@@ -30,5 +30,6 @@ We understand that certain privacy-minded users may not want to use the "website
- **Web vault:** Settings → Web Vault Options → Disable Website Icons
- **Browser extension:** Settings → Options → Disable Website Icons
- **Mobile app:** Settings → Options → Disable Website Icons
- **Desktop app:** Settings → Options → Disable Website Icons
When the website icons feature is disabled, Bitwarden will opt to show you a generic, locally accessed icon instead ({% icon fa-globe %}) that is the same for all login items stored in your vault.