ejabberd 26.07 (multiple security fixes): notice in lieu of pullup

[Greg Troxel <gdt%lexort.com@localhost>]

Long ago I wrote:

> Date: Fri, 25 Apr 2025 09:37:38 -0400 (1 year, 14 weeks, 4 days ago)
>
> Does anybody use erlang-* or ejabberd?  I'm asking because I don't
> perceive any users and am thus inclined to maintain ejabberd as "if it
> works for me it's good enough".

I have updated chat/ejabberd to 26.07, and updated a number of
erlang-foo.  It works for me (NetBSD 10 amd64), or I wouldn't have
committed it.

Nobody has said they're using ejabberd, so I will not request that 26.07
be pulled up to 2026Q2.  A pullup would require updates to a number of
erlang-foo (otherwise, ejabberd starts and throws stack traces at c2s
auth time).  I don't want to bite off the stability issues with other
erlang use, and I don't want to ask releng to spend time doing pullups
for which there are zero admitted users.  Doing

  cvs up -A */erlang* chat/ejabberd

and rebuilding worked for me.   I'm sure all zero of you can handle that!

But seriously, if you're using ejabberd, please let me know (here or
privately) and which OS/version/cpu/database/modules.