<pre style='margin:0'>
tobypeterson pushed a commit to branch master
in repository macports-ports.
</pre>
<p><a href="https://github.com/macports/macports-ports/commit/5c85b6b551945b81da3bc572effc4cc419265193">https://github.com/macports/macports-ports/commit/5c85b6b551945b81da3bc572effc4cc419265193</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'> new 5c85b6b munge: update to version 0.5.14
</span>5c85b6b is described below
<span style='display:block; white-space:pre;color:#808000;'>commit 5c85b6b551945b81da3bc572effc4cc419265193
</span>Author: A. Karl Kornel <karl@kornel.us>
AuthorDate: Mon Jan 27 21:53:20 2020 -0800
<span style='display:block; white-space:pre;color:#404040;'> munge: update to version 0.5.14
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> * Adds support for OpenSSL 1.1.0 (munge 0.5.13+)
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> * Switch to mungekey for initial key generation
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> A fresh install generates a key which MUNGE uses to secure
</span><span style='display:block; white-space:pre;color:#404040;'> communications between MUNGE daemons. Originally, this was done by
</span><span style='display:block; white-space:pre;color:#404040;'> `dd`-ing randomness into a file. Now MUNGE provides the mungekey(8)
</span><span style='display:block; white-space:pre;color:#404040;'> command for this (and other key-management) operation.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> * Disable test suite due to permissions checks
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> The MUNGE daemon will not run unless certain directories are secure.
</span><span style='display:block; white-space:pre;color:#404040;'> "Secure" means "owned by root" and "not accessible by others". This
</span><span style='display:block; white-space:pre;color:#404040;'> applies to where the MUNGE key lives. Less er restrictions (mainly
</span><span style='display:block; white-space:pre;color:#404040;'> "owned by root") are applied to all parent directories, up to the root.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> This does ot work well with MacPorts build directories. So until a
</span><span style='display:block; white-space:pre;color:#404040;'> solution is found, running the test suite during build time is disabled.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> * Enable autoreconf
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> The GitHub source no longer ships a configure script.
</span>---
net/munge/Portfile | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/net/munge/Portfile b/net/munge/Portfile
</span><span style='display:block; white-space:pre;color:#808080;'>index 4370c7c..ee22456 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/net/munge/Portfile
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/net/munge/Portfile
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -3,7 +3,7 @@
</span> PortSystem 1.0
PortGroup github 1.0
<span style='display:block; white-space:pre;background:#ffe0e0;'>-github.setup dun munge 0.5.12 munge-
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+github.setup dun munge 0.5.14 munge-
</span> revision 1
categories net security
license {GPL-3+ LGPL-3+}
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -22,11 +22,13 @@ long_description MUNGE (MUNGE Uid 'N' Gid Emporium) is an authentication \
</span> homepage https://dun.github.io/munge/
platforms darwin
<span style='display:block; white-space:pre;background:#ffe0e0;'>-checksums rmd160 0bc366a2d0a49875e7cf35ea2aebeef33490ed0c \
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- sha256 23585c1da3f4ea7c2882511c0a08220a2be13d9c03e54486bb8546791fa6c89b
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+checksums rmd160 e16e770d5c9697da521c6537ebcd3787357ef7dd \
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ sha256 1007d3ea6abd85f7712f5d2601ecb24c16b189ba5b0ec9aa563c11b7e0e9d600 \
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ size 274981
</span>
# We can either use OpenSSL or libgcrypt. Let's default to OpenSSL.
depends_lib-append path:lib/libssl.dylib:openssl
<span style='display:block; white-space:pre;background:#e0ffe0;'>+use_autoreconf yes
</span> configure.args --with-crypto-lib=openssl \
--with-openssl-prefix=${prefix}
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -40,8 +42,11 @@ variant libgcrypt description {Use libgcrypt for cryptographic routines} {
</span> --with-libgcrypt-prefix=${prefix}
}
<span style='display:block; white-space:pre;background:#ffe0e0;'>-# Allow doing testing
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-test.run yes
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+# The test suite is disabled, because when munged is run, it performs strict
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+# security checks on certain directories where munge data live. Those checks
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+# fail on the directory used for the build, and so any test that involve munged
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+# fails.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+test.run no
</span> test.target check
# Create some directories, with MUNGE-required permissions.
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -57,7 +62,7 @@ destroot.keepdirs-append ${destroot}${prefix}/etc/munge \
</span> # When activating, if a MUNGE key doesn't already exist, create a new one.
post-activate {
if {![file exists ${prefix}/etc/munge/munge.key]} {
<span style='display:block; white-space:pre;background:#ffe0e0;'>- system "dd if=/dev/urandom of=${prefix}/etc/munge/munge.key bs=1 count=1024"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ system "${prefix}/sbin/mungekey"
</span> file attributes ${prefix}/etc/munge/munge.key -permissions 0600
}
}
</pre><pre style='margin:0'>
</pre>