ame wrote= : > Il 19/05/2024 16:46, Jim Pazarena ha scritto: > > I upgraded both of the captioned versions at the same time, so it is no= t > > clear to me which is causing this issue.. however, since upgrading, > > often but without any discernible cycle or frequency, exim refuses > > incoming connections, and logs the following: > > > > 2024-05-19 07:21:00 SIGSEGV (fault address: 0xffffffffffffff70) > > 2024-05-19 07:21:00 SIGSEGV (maybe attempt to write to immutable memory= ) > > Maybe exim is violating some policy? > What does sysctl kern.elf${your_arch}.allow_wx say? > > FreeBSD14 features some pretty memory protections: see mitigations(7). > Bye, > f > I am running the same version of Exim on the same version of FreeBSD (on two different servers, no custom kernel) and I haven't seen these symptoms. If anything, here is the output of what you asked: `` wash@gw:~$ sysctl -a | grep allow_wx kern.elf32.allow_wx: 1 kern.elf64.allow_wx: 1 ``` But I did not configure these. --=20 Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] --0000000000009906c20618f3f671 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Sun, May 19, 2024 at 7:24=E2=80=AF= PM tetrosalame <tml= @seiruote.it> wrote:

Il 19/05/2024 16:46, Jim Pazarena ha scritto:
> I upgraded both of the captioned versions at the same time, so it is n= ot
> clear to me which is causing this issue.. however, since upgrading, > often but without any discernible cycle or frequency, exim refuses > incoming connections, and logs the following:
>
> 2024-05-19 07:21:00 SIGSEGV (fault address: 0xffffffffffffff70)
> 2024-05-19 07:21:00 SIGSEGV (maybe attempt to write to immutable memor= y)

Maybe exim is violating some policy?
What does sysctl kern.elf${your_arch}.allow_wx say?

FreeBSD14 features some pretty memory protections: see mitigations(7).
Bye,
f

<= div>

I am running the same version of Exim on the s= ame version of FreeBSD (on two different servers, no custom kernel) and I h= aven't seen these symptoms.

If anything, here is the output of what you asked:

wash@gw:~$ sysctl -a | grep allow_wx
kern.elf32.allow_wx:= 1
kern.elf64.allow_wx: 1

```

<= br>

But I did not c= onfigure these.

= --

<= div dir=3D"ltr">

Best regards,
Odhiambo WASHINGTON,
Nairobi,KE+254 7 3200 0004/+254 7 2274 3223

=C2=A0In=C2=A0an Internet = failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.",=C2=A0egrep -v '^$|^.*= #'=C2=A0=C2=AF\_(=E3=83=84)_/=C2=AF=C2=A0:-)

[How to ask smart questions:=C2=A0http://www.catb.org/~esr/faqs/smart-questions.html]=

--0000000000009906c20618f3f671--