aboutsummaryrefslogtreecommitdiff
path: root/argparse/bulk.yaml
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-19 18:37:21 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-19 18:37:21 -0800
commitac2bfc709f57094bac54b299f0a307b765e9b674 (patch)
tree8e8e040559ca05883445b772bbcbd042cbb510ee /argparse/bulk.yaml
parentcaa78070f52841191576c4704ebcafd55af0224f (diff)
downloadnitrocli-ac2bfc709f57094bac54b299f0a307b765e9b674.tar.gz
nitrocli-ac2bfc709f57094bac54b299f0a307b765e9b674.tar.bz2
Introduce SecretEntry trait
Now that we have introduced the notion of a secret abstracting over whether something is a PIN or a password in terms of terminology, we need to define what makes a secret in code. From the pinentry module's perspective, the commonality between the two is that they both can be entered through a dialog containing a prompt and a description, and they can be cached. This change introduces a trait, SecretEntry, that defines methods representing those properties. Right now only the existing PinEntry struct implements this trait.
Diffstat (limited to 'argparse/bulk.yaml')
0 files changed, 0 insertions, 0 deletions