Date: Sat, 27 Aug 2022 15:02:04 +0200 From: Michael Gmelin <grembo@freebsd.org> To: FreeBSD User <freebsd@walstatt-de.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org>, yasu@freebsd.org Subject: Re: security/clamav: /ar/run on TMPFS renders the port broken by design Message-ID: <DBF99D65-0BAE-485F-90EB-42CC3E080161@freebsd.org> In-Reply-To: <20220827125405.10194d30@thor.intern.walstatt.dynvpn.de> References: <20220827125405.10194d30@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 27. Aug 2022, at 12:54, FreeBSD User <freebsd@walstatt-de.de> wrote: >=20 > =EF=BB=BFAm Sat, 27 Aug 2022 11:21:40 +0200 > Michael Gmelin <grembo@freebsd.org> schrieb: >=20 >>>> On 27. Aug 2022, at 08:31, FreeBSD User <freebsd@walstatt-de.de> wrote:= >>>=20 >>> =EF=BB=BFHello, >>>=20 >>> I'm referencing to Bug 259699 [2] and Bug 259585 [1]. >>>=20 >>> Port security/clamav is without doubt for many of FreeBSD users an impor= tant piece of >>> security software so I assume a widespread usage. >>>=20 >>> It is also a not uncommon use case to use NanoBSD or any kind of low-mem= ory-footprint >>> installation schemes in which /var/run - amongst other system folders - a= re created at boot >>> time as TMPFS and highly volatile. >>>=20 >>> In our case, the boxes running a small security appliance based upon Fre= eBSD is rebooted >>> every 24 hours and so /var/run is vanishing. >>>=20 >>> To make the long story short: >>>=20 >>> The solution for this problem would be a check for existence and take ac= tion addendum in >>> precmd() routine of the rc-script as sketched in Bug 259699. >>> The maintainer rejects such a workaround by arguing this would violate P= OLA (see comment 4 >>> in PR 259699 [2]. The maintainer's argument regaring to mtree's files ar= e sound to me. >>>=20 >>> The question is: how can this issue be solved? >>>=20 >>> It is really hard to always chenge our local repository and patch whenev= er clamav has been >>> patched and modified for what reason ever. >>>=20 >>> Tahanks for reading, >>>=20 >>=20 >> Why don=E2=80=99t you simply add an rc script to your appliance that crea= tes the missing >> directory/directories on boot before clamav is started? >>=20 >> Best >> Michael >>=20 >>=20 >>=20 >=20 > Why not fixing this on a more general basis? It=E2=80=98s a reasonable way forward, given the limitations you described (= you=E2=80=99re removing /var/run, which shouldn=E2=80=99t be removed and the= port maintainer not willing to add code to compensate for this). This would= fix it for you for your specific needs in a reliable way, you would never h= ave to patch the port again and also won=E2=80=99t use other people=E2=80=98= s time to find a general solution to your very specific problem. It=E2=80=99= s a sustainable quick fix to your problem at hand. You can always come up wi= th something grand later, but this would actually work right away. Cheers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBF99D65-0BAE-485F-90EB-42CC3E080161>