diff options
| author | spwhitton <spwhitton@web> | 2017-05-10 01:29:15 +0000 |
|---|---|---|
| committer | admin <admin@branchable.com> | 2017-05-10 01:29:15 +0000 |
| commit | f19e202a2f93054a5e037e40ba8722f449a69793 (patch) | |
| tree | 2d465c8f80798fd9761ae0b50b2f6124aa3c3226 | |
| parent | 67a93226494f159d4210153ef9ef7c5546702628 (diff) | |
| download | debug-me-f19e202a2f93054a5e037e40ba8722f449a69793.tar.gz | |
post feature suggestion
| -rw-r--r-- | doc/todo/use_distribution_keyrings.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/use_distribution_keyrings.mdwn b/doc/todo/use_distribution_keyrings.mdwn new file mode 100644 index 0000000..0191b13 --- /dev/null +++ b/doc/todo/use_distribution_keyrings.mdwn @@ -0,0 +1,5 @@ +In addition to the web-of-trust checking debug-me already does, it could also inform the user whether keys are present in distribution keyrings, such as `/usr/share/keyrings/debian-keyring.gpg`. This would be especially relevant when it is distribution issues that are to be debugged with debug-me: the person connecting is also capable of pushing updates to the usre's machine. + +Distribution packagers of debug-me could add the keyrings to be checked in this way to a configuration file, or possibly just hardcode them somewhere in debug-me's source. + +--spwhitton |