Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
heinrich-ulbricht committed Dec 10, 2017
2 parents fff4a86 + a599393 commit e84df5e
Showing 1 changed file with 12 additions and 3 deletions.
15 changes: 12 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
Export tagged entries to a new password database every time you save. The new database can use a different password.

# What does it do?
Every time you save your database a new database will be created and passwords with certain tags will be copied over (in KeePass you can mark any password entry with tags).
Every time you save your database a new database will be created and passwords with certain tags will be copied over (in KeePass you can mark any password entry with tags). No user interaction is required, the whole process runs in the background.

The new file is created in the same folder as your database file. If your database file is *passwords.kdbx* the new file will be named *passwords.partial-!readonly!.kdbx*. This file will be overwritten __every time__ you save the original database, so don't make any changes to the copy.
Without further configuration the new file is created in the same folder as your database file. If your database file is *passwords.kdbx* the new file will be named *passwords.partial-!readonly!.kdbx*. This file will be overwritten __every time__ you save the original database, so don't make any changes to the copy. (Note: as of v1.1.0 you can change output path and file name. The same reasoning applies, make sure to not overwrite existing files.)

The new database can be protected with a password different from the original database's one. Key files and Windows account are not supported.

Expand Down Expand Up @@ -36,6 +36,16 @@ The tags of this entry are the tags the plugin looks for. Passwords having those
# Advanced Configuration
Note: this section assumes you created the special password entry *PartialExportConfig* as described above.

## Set output file path and name (v1.1.0)
You can use the *URL* field of the *PartialExportConfig* to specify file name and/or path of the exported database file.

Supported values are:
* absolute pathes (*C:\OneDrive\PartialExport.kdbx*)
* relative pathes (*Export/PartialExport.kdbx*, *../PartialExport.kdbx*) - they will be resolved relative to the current database
* no path (*PartialExport.kdbx*) - will export to the directory of the current database

The *kdbx* file extension will be added automatically if missing.

## Clear *otp* string field
For the *PartialExportConfig* entry create a string field with name *clearotp* to NOT export the *otp* string field of entries to the new database. The *otp* field is used by the [KeeOtp](https://keepass.info/plugins.html#keeotp) plugin to store the secret key for one-time password generation. If you use other devices to generate one-time passwords you might want to exclude those keys from the exported database to not expose them to attackers.

Expand All @@ -45,5 +55,4 @@ Note: the value of the *clearotp* field doesn't matter and can be empty.

* **the group/folder structure is not copied** - the exported database will have the root folder containing all exported passwords
* export to only one file
* file name and location can not be configured - it's always exported to the same folder as original database, with hardcoded name extension
* the new database can only be protected by password, not key files or a Windows account

0 comments on commit e84df5e

Please sign in to comment.