Acknowledgement sent to Luigi Bai <firstname.lastname@example.org>:
New bug report received and forwarded. Copy sent to email@example.com.
Your message specified a Severity: in the pseudo-header, but
the severity value important was not recognised.
The default severity normal is being used instead.
The recognised values are: critical, grave, normal, minor, wishlist.
To: Devuan Bug Tracking System <firstname.lastname@example.org>
Subject: apparmor: Add /etc/mdns.allow to abstractions/mdns
Date: Sat, 27 Apr 2019 10:04:39 -0500
* What led up to the situation?
Executables protected by apparmor cannot reach MDNS suffixes declared in
/etc/mdns.allow, and probed by libnss-mdns.
Please see /usr/share/doc/libnss-mdns/README.md.gz in package libnss-mdns.
* What exactly did you do (or not do) that was effective (or
Attempt to use, e.g., ntpd to connect to an MNDS domain that isn't .local.
* What was the outcome of this action?
Failure, and a DENIED entry in the kernel to /etc/mdns.allow
* What outcome did you expect instead?
access to the host on the non-.local MDNS domain.
Proposed fix: add /etc/mnds.allow to abstractions/mnds.
This fix works for me.
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux beowulf/ceres
Kernel: Linux 4.19.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages apparmor depends on:
ii debconf [debconf-2.0] 1.5.71
ii libc6 2.28-8
ii lsb-base 10.2019031300
ii python3 3.7.2-1
apparmor recommends no packages.
Versions of packages apparmor suggests:
pn apparmor-profiles-extra <none>
ii apparmor-utils 2.13.2-10
-- Configuration Files:
/etc/apparmor.d/abstractions/mdns changed [not included]
-- debconf information excluded