Pablo Abelenda <pabele...@igalia.com> writes:

> Package: mandos
> Version: 1.6.9
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> I've been making a mandos server setup. The service and the servers
> it has to unlock are running on different networks and, due to this,
> zeroconf is not useful for me. As I was not using zeroconf, avahi
> service was not running while running all my tests.
>
> Thing is that, while starting up mandos server with the init script,
> I obtained the following error:
>
> --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
> ERROR: Introspect error on org.freedesktop.Avahi:/: \
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.FileInvalid: \
> Cannot do system-bus activation with no user
> --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
>
> I asked myself why was mandos trying to communicate with Avahi if
> I have configured zeroconf to be false? I then tried to manually
> run the service like this:
>
> mandos --no-zeroconf
>
> This time the service started up correctly.
>
> Taking a look around I ended up on the options parsing section of
> /usr/sbin/mandos. Seems like zeroconf option is missing there,
> therefore, not matter True or False, service will be always trying
> to use zeroconf, as the default value is True.
>
> --- mandos.orig       2017-02-20 15:11:40.228977179 +0100
> +++ mandos    2017-02-20 15:12:18.381015090 +0100
> @@ -2370,7 +2370,7 @@
>      # Convert the SafeConfigParser object to a dict
>      server_settings = server_config.defaults()
>      # Use the appropriate methods on the non-string config options
> -    for option in ("debug", "use_dbus", "use_ipv6", "foreground"):
> +    for option in ("debug", "use_dbus", "use_ipv6", "foreground", 
> "zeroconf"):
>          server_settings[option] = server_config.getboolean("DEFAULT",
>                                                             option)
>      if server_settings["port"]:
>
> With this little modification, things started to work as expected.
>
> I've also looked to the sid package as well, and seems to be having
> the same issue.
>
> Many thanks in advance for taking care of this.

Many thanks for the bug report and fix!  It seems the "restore" options
was also affected by the same bug.  I have committed a fix to trunk; I
will make a full release with this after I have made some tests.

/Teddy Hogeborn

-- 
The Mandos Project
https://www.recompile.se/mandos

Attachment: signature.asc
Description: PGP signature

Reply via email to