Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(266)

Side by Side Diff: docs/linux_password_storage.md

Issue 1324603002: [Docs] Another round of stylistic fixes. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/linux_open_suse_build_instructions.md ('k') | docs/linux_pid_namespace_support.md » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Introduction 1 # Linux Password Storage
2 2
3 On Linux, Chromium can store passwords in three ways: 3 On Linux, Chromium can store passwords in three ways:
4 * GNOME Keyring
5 * KWallet 4
6 * plain text
7 Chromium chooses which store to use automatically, based on your desktop environ ment.
8 4
9 Passwords stored in GNOME Keyring or KWallet are encrypted on disk, and access t o them is controlled by dedicated daemon software. Passwords stored in plain tex t are not encrypted. Because of this, when either GNOME Keyring or KWallet is in use, any unencrypted passwords that have been stored previously are automatical ly moved into the encrypted store. 5 * GNOME Keyring
6 * KWallet 4
7 * plain text
10 8
11 Support for using GNOME Keyring and KWallet was added in version 6, but using th ese (when available) was not made the default mode until version 12. 9 Chromium chooses which store to use automatically, based on your desktop
10 environment.
12 11
13 # Details 12 Passwords stored in GNOME Keyring or KWallet are encrypted on disk, and access
13 to them is controlled by dedicated daemon software. Passwords stored in plain
14 text are not encrypted. Because of this, when either GNOME Keyring or KWallet is
15 in use, any unencrypted passwords that have been stored previously are
16 automatically moved into the encrypted store.
14 17
15 Although Chromium chooses which store to use automatically, the store to use can also be specified with a command line argument: 18 Support for using GNOME Keyring and KWallet was added in version 6, but using
16 * `--password-store=gnome` (to use GNOME Keyring) 19 these (when available) was not made the default mode until version 12.
17 * `--password-store=kwallet` (to use KWallet)
18 * `--password-store=basic` (to use the plain text store)
19 20
20 Note that Chromium will fall back to `basic` if a requested or autodetected stor e is not available. 21 ## Details
21 22
22 In versions 6-11, the store to use was not detected automatically, but detection could be requested with an additional argument: 23 Although Chromium chooses which store to use automatically, the store to use can
23 * `--password-store=detect` 24 also be specified with a command line argument:
25
26 * `--password-store=gnome` (to use GNOME Keyring)
27 * `--password-store=kwallet` (to use KWallet)
28 * `--password-store=basic` (to use the plain text store)
29
30 Note that Chromium will fall back to `basic` if a requested or autodetected
31 store is not available.
32
33 In versions 6-11, the store to use was not detected automatically, but detection
34 could be requested with an additional argument:
35
36 * `--password-store=detect`
OLDNEW
« no previous file with comments | « docs/linux_open_suse_build_instructions.md ('k') | docs/linux_pid_namespace_support.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698