summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorspwhitton <spwhitton@web>2017-05-10 16:01:42 +0000
committeradmin <admin@branchable.com>2017-05-10 16:01:42 +0000
commit581e8f724a66fc5c57f28d99353e08211127e932 (patch)
treea4699d9e6bbf87db1dfd32605301f68ba868458f
parentf19e202a2f93054a5e037e40ba8722f449a69793 (diff)
downloaddebug-me-581e8f724a66fc5c57f28d99353e08211127e932.tar.gz
add example output to feature suggestion
-rw-r--r--doc/todo/use_distribution_keyrings.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/use_distribution_keyrings.mdwn b/doc/todo/use_distribution_keyrings.mdwn
index 0191b13..df21588 100644
--- a/doc/todo/use_distribution_keyrings.mdwn
+++ b/doc/todo/use_distribution_keyrings.mdwn
@@ -1,5 +1,7 @@
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.
+Example output: `Sean Whitton is an official Debian Developer (information accurate as of YYYY-MM-DD)` where the date comes from the version of the `debian-keyring` package.
+
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