summaryrefslogtreecommitdiff
path: root/security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys
diff options
context:
space:
mode:
Diffstat (limited to 'security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys')
-rw-r--r--security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys11
1 files changed, 11 insertions, 0 deletions
diff --git a/security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys b/security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys
new file mode 100644
index 000000000000..9b80668e0f86
--- /dev/null
+++ b/security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys
@@ -0,0 +1,11 @@
+--- examples/monkeysphere-monitor-keys.orig 2018-10-16 16:24:55 UTC
++++ examples/monkeysphere-monitor-keys
+@@ -31,7 +31,7 @@
+
+ # FIXME: does this handle revocations and re-keying? if a sysadmin
+ # switches over to this arrangement, how will the system check for
+-# revocations? Scheduling a simple gpg --refresh should handle
++# revocations? Scheduling a simple gpg2 --refresh should handle
+ # revocations. I'm not sure how to best handle re-keyings.
+
+ use strict;