Scott Kitterman:
> >> I was just reviewing the 3.7 development changelog and didn't see 20211115
> >> listed. Is this fix still planned?
> >
> >The fix is in the 3.7 code, but I forgot to update the HISTORY file.
> >It is also planned for the next stable releases, together with the
> >fix below.
> >
> >These are low-priority fixes, so expect to see these early January.
> >
> > Wietse
> >
> >20211216
> >
> > Bugfix (introduced: Postfix 3.0): the proxymap daemon did not
> > automatically authorize proxied maps inside pipemap (example:
> > pipemap:{proxy:maptype:mapname, ...}) or inside unionmap. Problem
> > reported by Mirko Vogt. Files: proxymap/proxymap.c.
>
> Thanks. Certainly no rush. I only wanted to make sure it wasn't forgotten.
>
> Any chance of the glibc-2.34 fix being in there too? We haven't
> switched, so not a rush directly for Debian, but some of our
> downstreams have, so it would be nice to see.
What is 'the glibc-2.34 fix'? closefrom() ?
I have been backporting GLIBC workarounds for broken DNSSEC support
and they seem to be ignored. Example from Postfix 3.5.1:
Workaround for broken DANE support after an incompatible
change in GLIBC 2.31. THIS AVOIDS THE NEED FOR NEW OPTIONS
IN /etc/resolv.conf. Files: dns/dns.h, dns/dns_lookup.c.
I was not impressed with the lack of uptake by distros. That makes
me less motivated to spend time backporting GLIBC workarounds for
trivial problems like closefrom.
Wietse
