From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bind: should be built without seccomp
Date: Sat, 30 Jan 2021 02:14:26 +0100 [thread overview]
Message-ID: <20210130011426.HPKS9D21dwKL9LYcfaurAC4oXN3li83tlahEsG4WF0w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11436@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Closed issue by lonwillett on void-packages repository
https://github.com/void-linux/void-packages/issues/11436
Description:
### System
* xuname: Void 5.0.10_1 x86_64-musl GenuineIntel/PV uptodate hold rrnFFFFFF
* package: bind-9.11.6_1
### Expected behavior
Works
### Actual behavior
I have had repeated issues with bind and seccomp. The latest...
Message:
2019-04-30T05:57:44.14997 kern.notice: [735346.896514] audit: type=1326 audit(1556603864.148:10): auid=4294967295 uid=800 gid=800 ses=4294967295 pid=17441 comm="named" exe="/usr/bin/named" sig=31 arch=c000003e syscall=302 compat=0 ip=0x7f7283c632c4 code=0x0
Then it fails to work correctly: some threads die, behaviour is erratic.
### Steps to reproduce the behavior
I admit that I have not figured out precisely what the problem is. Possbily related to using musl instead of glibc. However, the problems disappear when I build bind without seccomp support. And when I googled for similar things, I found:
https://gitlab.isc.org/isc-projects/bind9/issues/93
So it appears to me that there is no real reason to enable the seccomp support in bind. It will be disappearing anyway, and provides little improvement in security.
next prev parent reply other threads:[~2021-01-30 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11436@inbox.vuxu.org>
2021-01-30 1:14 ` ericonr
2021-01-30 1:14 ` ericonr [this message]
2021-01-30 1:14 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210130011426.HPKS9D21dwKL9LYcfaurAC4oXN3li83tlahEsG4WF0w@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).