No worries Michael! Yes we're doing traversal from root to avoid that issue.
:-)
Kevin: Any chance you can upgrade those old systems? We try to support roughly
the last 2 LTS releases for major distros / operating systems but don't have
time to go out of our way to maintain compatibility wit
Achtung, falscher Empfänger
-Ursprüngliche Nachricht-
Von: clamav-users Im Auftrag von Mark
Fortescue via clamav-users
Gesendet: Freitag, 17. Juli 2020 12:46
An: clamav-users@lists.clamav.net
Cc: Mark Fortescue
Betreff: Re: [clamav-users] Problems compiling 0.102.4 on OLD system
Hi
Hi Kevin,
It looks like you will have to create/enable private versions of the
openat(), ranameat() and unlinkat() functions.
These can be simulated using regular C functions open(), unlink(),
rename(), stat() and readdir().
You will need to get manual pages for openat(), ranameat() and
un
On 2020-07-16 19:10, Michael Orlitzky via clamav-users wrote:
>
> Micah: openat() only provides "one level of safety" in that when opening
> /foo/bar/baz, it ensures that "baz" is where you think it is. You may
> want to investigate whether or not an attacker can replace "bar" by a
> symlink in th
On 2020-07-16 17:22, Kevin A. McGrail via clamav-users wrote:
> Hi, I have an old system I'm compiling.
>
> I have 0.102.3 working on it.
>
> Here's the config line:
>
> ...
> CCLD clamscan
> actions.o: In function `traverse_to':
> ../shared/actions.c:328: undefined reference to `openat'
>
Hi, I have an old system I'm compiling.
I have 0.102.3 working on it.
Here's the config line:
CC=/usr/local/gcc4.2.4/bin/gcc ./configure --prefix=/usr/local/clamav
--with-user=defang --with-group=defang --enable-llvm=no
--with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre2
--with-zlib=/usr/
