On 22/05/2022 15:57, Bill Cole via Exim-users wrote:
I'm unclear on why the option even exists. It seems crippling.
See also
http://exim.org/exim-html-current/doc/html/spec_html/ch-security_considerations.html#SECTrunexiwitpri
and (separately) think about what might be feasible if inetd or sy
On 2022-05-22 at 05:47:12 UTC-0400 (Sun, 22 May 2022 10:47:12 +0100)
Jeremy Harris via Exim-users
is rumored to have said:
> On 22/05/2022 10:30, Axel Rau via Exim-users wrote:
>> So it is a standard FreeBSD ports installation and therefor not setuid root.
>
> If that is standard for FreeBSD
It
On 22/05/2022 10:30, Axel Rau via Exim-users wrote:
So it is a standard FreeBSD ports installation and therefor not setuid root.
If that is standard for FreeBSD then you need to ask them why it's
nonfunctional.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/
> Am 21.05.2022 um 20:25 schrieb Bill Cole via Exim-users :
>
> Do you have AppArmor or SELinux enabled? What user and group is Exim running
> as?
This is FreeBSd 13.0
root@lists5:/var/log # ps -axlw | grep exim
26 67908 1 15 20 0 22484 9888 select IsJ - 0:00.24
/usr/sbin/sendmail
> Am 21.05.2022 um 21:25 schrieb Jeremy Harris via Exim-users
> :
>
> Also, is this a "vanilla" Exim installation, with the Exim binary
> setuid root (Exim usually needs that so it can deliver to local
> user mailbox files. But it runs most of the time with dropped
> privs).
Ah, set’s the poin
