diff options
| author | VinÃcius Zavam <egypcio@FreeBSD.org> | 2019-02-25 14:43:23 +0000 |
|---|---|---|
| committer | VinÃcius Zavam <egypcio@FreeBSD.org> | 2019-02-25 14:43:23 +0000 |
| commit | b1d97de0ca1dd07482dd6f92c6652ae020386f1c (patch) | |
| tree | 3882b965c464e382e9d154ded2e3830f5d2af5fe /security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys | |
| parent | [NEW PORT] security/ssllabs-scan: Command-line tool to use the SSL Labs API (diff) | |
security/monkeysphere: update 0.41 to 0.42
- Makefile
adopt the port;
pet portlint;
remove comment about 'applying patches' on the post-patch stage;
unmute post-patch.
- files/*
patch src/share/mh/revoke_keys, to use gpg2;
move patch-gpg2 (410 lines), and split it to have separated patches;
regen all patches using makepatch.
Approved by: rene (mentor)
Differential Revision: https://reviews.freebsd.org/D18871
Diffstat (limited to 'security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys')
| -rw-r--r-- | security/monkeysphere/files/patch-examples_monkeysphere-monitor-keys | 11 |
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; |
