X-Git-Url: https://git.dogcows.com/gitweb?p=chaz%2Fp5-File-KDBX;a=blobdiff_plain;f=lib%2FFile%2FKDBX%2FKey.pm;h=b44faca9183c117e95cd70457ba03127a903485b;hp=8a5796568bd9c2c2d03a6d97723826a5245e4c02;hb=63d73bf382edfb0089b36a45193fc2835cb58b6d;hpb=de4c4c788a24dd5af457ee5ad2006e8f60415ce9 diff --git a/lib/File/KDBX/Key.pm b/lib/File/KDBX/Key.pm index 8a57965..b44faca 100644 --- a/lib/File/KDBX/Key.pm +++ b/lib/File/KDBX/Key.pm @@ -160,8 +160,8 @@ sub _clear_raw_key { $key = $key->hide; -Put the raw key in L. Does nothing if the raw key is already in memory -protection. Returns itself to allow method chaining. +Put the raw key in L. Does nothing if the raw key is already +in memory protection. Returns itself to allow method chaining. =cut @@ -214,7 +214,7 @@ There are several different types of keys, each implemented as a subclass: =for :list * L - Password or passphrase, knowledge of a string of characters -* L - Possession of a file ("key file") with a secret. +* L - Possession of a file ("key file") with a secret * L - Possession of a device that responds correctly when challenged * L - Possession of a YubiKey hardware device (a type of challenge-response) * L - One or more keys combined as one @@ -227,11 +227,11 @@ password key by itself. (Of course it's much better to not have any weak compone B Most KeePass implementations are limited in the types and numbers of keys they support. B keys are pretty much universally supported. B keys are pretty well-supported. Many do not support challenge-response keys. If you are concerned about compatibility, you should stick with one of these -configurations: +well-supported configurations: =for :list * One password * One key file -* One password and one key file +* Composite of one password and one key file =cut