This is the same as bug #1094097.
The failed test output shows this error:
> munged: Error: Logfile is insecure: invalid ownership of "/tmp"
The preconditions for that error are here:
https://sources.debian.org/src/munge/0.5.16-1/src/munged/path.c/#L224
munged is checking for that directory t
Did the ownership of /tmp change? I would expect that directory to be
owned by root. I'm unable to reproduce this failure on my sid test vm
(where /tmp is owned by root and permissioned 1777). But I can
reproduce it if I chown /tmp to bin or somesuch.
The failed tests show this error which
Patches 1-3 are for the sharness test suite and are only needed if you're
running 'make check'. Patch 4 fixes the actual bug. Stack applies cleanly
against 0.5.14. Tested on s390x.
From c593d4ff7b1fc37bb67bffaa1e0a896b136fdff6 Mon Sep 17 00:00:00 2001
From: Chris Dunlap
Date: Fri
munge-0.5.13 adds support for getrandom() (which was added to glibc
in v2.25). munged calls getrandom() once during its initialization.
getrandom() will block until its entropy pool has been initialized,
after which it never blocks for reads of up to 256 bytes.
You mention that you're running in
I've applied the patch to the master branch (commit d6c235b).
It will be in the next release.
-Chris
On Thu, 2013-10-24 at 01:38pm +0200, oliv...@na.icar.cnr.it wrote:
>
> On Wed, Oct 23, 2013 at 04:42:04PM -0700, Chris Dunlap wrote:
> > munge-0.5.11 was released 2013-08
munge-0.5.11 was released 2013-08-27. It includes updated
config.{guess,sub} files.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: exmh
Version: 1:2.7.2-16
Severity: normal
Tags: patch
GPG encryption from within exmh is not recognizing the "default-key"
setting specified in GPG's default config file. This affects the
default signing key as well as the sender's key that is automatically
added as a GPG-recipient (whic
7 matches
Mail list logo
