summaryrefslogtreecommitdiff
path: root/libc/Cargo.lock
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-09 15:29:35 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-09 15:29:35 -0800
commit4e83e8f9a79bcd26435b66d9faed72ff98a45555 (patch)
tree35673af41ce1f53a8da5996bcf7604758456c668 /libc/Cargo.lock
parent17203a1a5d91a1749adeca0f108aad8efa979ff3 (diff)
downloadnitrocli-4e83e8f9a79bcd26435b66d9faed72ff98a45555.tar.gz
nitrocli-4e83e8f9a79bcd26435b66d9faed72ff98a45555.tar.bz2
Use 'pin' instead of 'passphrase'
In the past we have used the term 'passphrase' to refer to the data retrieved through the pinentry module and that terminology has permeated the commands module as well. However, on the Nitrokey side we talk about PINs most of the time (despite a lack of an requirement for being actual numbers). In an attempt to unify terminology a bit more, this change renames all occurrences of the term 'passphrase' with PIN. This renaming has the nice side effect of making the code more concise because the latter is much shorter than the former.
Diffstat (limited to 'libc/Cargo.lock')
0 files changed, 0 insertions, 0 deletions