mirror of
https://github.com/keepassxreboot/keepassxc.git
synced 2024-10-01 01:26:01 -04:00
Fix typos in various .md files
This commit is contained in:
parent
dc42d5dda6
commit
cb28329f14
@ -1,6 +1,6 @@
|
||||
---
|
||||
name: Release Preview Bug report
|
||||
about: report a bug with a release preview (eg, 2.4.0-beta1)
|
||||
about: report a bug with a release preview (e.g., 2.4.0-beta1)
|
||||
title: "[PRE-RELEASE] "
|
||||
labels: PRE-RELEASE BUG
|
||||
assignees: droidmonkey
|
||||
|
@ -1,7 +1,7 @@
|
||||
# List of Keyboard Shortcuts for KeepassXC
|
||||
# List of Keyboard Shortcuts for KeePassXC
|
||||
|
||||
Actions | Keyboard Shortcuts
|
||||
---------------------------|----------------------------
|
||||
-----------------------------|----------------------------
|
||||
New Database | Ctrl + Shift + N
|
||||
Open Database | Ctrl + O
|
||||
Save Database | Ctrl + S
|
||||
@ -18,18 +18,14 @@ Copy TOTP | Ctrl + T
|
||||
Copy Username | Ctrl + B
|
||||
Copy Password | Ctrl + C
|
||||
Trigger AutoType | Ctrl + Shift - V
|
||||
Open Url | Ctrl + Shift - U
|
||||
Copy Url | Ctrl + U
|
||||
Open URL | Ctrl + Shift - U
|
||||
Copy URL | Ctrl + U
|
||||
Show Minimized | Ctrl + M
|
||||
Hide Window | Ctrl + Shift - M
|
||||
Select Next Database Tab | Ctrl + Tab *OR* Ctrl + PGDN
|
||||
Select Previous Datase Tab | Ctrl + Shift + Tab *OR* Ctrl + PGUP
|
||||
Select Previous Database Tab | Ctrl + Shift + Tab *OR* Ctrl + PGUP
|
||||
Toggle Passwords Hidden | Ctrl + Shift + C
|
||||
Toggle Usernames Hidden | Ctrl + Shift + B
|
||||
Focus Search | Ctrl + F
|
||||
Clear Search | ESC
|
||||
Show Keyboard Shortcuts | Ctrl + /
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -120,14 +120,14 @@ There is a simple overview of shared groups to keep track of your data.
|
||||
|
||||
## Technical Details and Limitations of Sharing
|
||||
|
||||
Sharing relies on the combination of file exports and imports as well as the synchronization mechanism provided by KeePassXC. Since the merge algorithm uses the history of entries to prevent data loss, this history must be enabled and have a sufficient size. Furthermore, the merge algorithm is location independend, therefore it does not matter if entries are moved outside of an import group. These entries will be updated none the less. Moving entries outside of export groups will prevent a further export of the entry, but it will not ensure that the already shared data will be removed from any client.
|
||||
Sharing relies on the combination of file exports and imports as well as the synchronization mechanism provided by KeePassXC. Since the merge algorithm uses the history of entries to prevent data loss, this history must be enabled and have a sufficient size. Furthermore, the merge algorithm is location independent, therefore it does not matter if entries are moved outside of an import group. These entries will be updated none the less. Moving entries outside of export groups will prevent a further export of the entry, but it will not ensure that the already shared data will be removed from any client.
|
||||
|
||||
KeeShare uses a custom certification mechanism to ensure that the source of the data is the expected one. This ensures that the data was exported by the signer but it is not possible to detect if someone replaced the data with an older version from a valid signer. To prevent this, the container could be placed at a location which is only writeable for valid signers.
|
||||
|
||||
## Using Auto Open
|
||||
|
||||
The Auto Open feature automatically loads and unlocks additional databases when you unlock your main database.
|
||||
In order to use this functionnality, do the following:
|
||||
In order to use this functionality, do the following:
|
||||
|
||||
1. Create a group called **AutoOpen** at the root of your main database.
|
||||
1. In this group, create a new entry for each database that should be opened automatically:
|
||||
|
@ -9,7 +9,7 @@ can connect and access the exposed database in KeePassXC.
|
||||
## Configurable settings
|
||||
|
||||
* The user can specify if a database is exposed on DBus, and which group is exposed.
|
||||
* Whether to show desktop notification is shown when an entry is retrived.
|
||||
* Whether to show desktop notification is shown when an entry is retrieved.
|
||||
* Whether to skip confirmation for entries deleted from DBus
|
||||
|
||||
## Implemented Attributes on Item Object
|
||||
|
Loading…
Reference in New Issue
Block a user