Description of problem:
cyrus-sasl-2.1.10-4 is linked against threaded libdb-4.0, that can
cause bigger problems. This was the reason to bundle a libdb with
cyrus-sasl (see changelog from cyrus-sasl-2.1.17-1), but at Red
Hat Linux 9 this wasn't done. So "Very Bad Things" can happen...
Version-Release number of selected component (if applicable):
How reproducible & Steps to Reproduce:
That there can be problems is described in #112215
I think, the onliest solution is to bundle a non-threaded libdb-4.0
also with cyrus-sasl-2.1.10-4 (Red Hat Linux 9) to prevent "Very Bad
Things" in the same way as it was done with cyrus-sasl-2.1.18-2 at
A good and working solution (and no "notabug" or "worksforme") before
the End-Of-Lifetime of Red Hat Linux 9 is reached...thank you very
Seems so, that there is a patch needed, that libdb-4 is bundable
with cyrus-sasl-2.1.10-4, because my simple hack failed building.
Well, the abuse to you about the current working status you can read
in bug #120558, I think one time writing that is enough ;-)
But after EOL is reached now, I think you'll close this bug - sooner
or later - relatively sure with "notabug", "worksforme" or something
But I still hacked a solution out, so that others maybe affected by
that problem, can find a (for me) working solution here. The onliest
thing to make me just a little bit friendlier would be to verify and
approve my solution, if it is right (whether it doesn't take too much
FYI: My hack should - maybe merged - also work at cyrus-imapd,
openldap, etc of Red Hat Linux 9.
Created attachment 101002 [details]
Diff between spec file of cyrus-sasl of RHL9 and my hack (latest cyrus-sasl)
My hack also should work with the original cyrus-sasl delivered with RHL9.
Created attachment 101003 [details]
Created attachment 101004 [details]
Created attachment 101005 [details]
Created attachment 101006 [details]
For those, who want or need it...
Nice, that I got full qualified and useful answers</irony>
I'll close this bug report with "worksforme" now, because Red Hat
Linux 9's time to live is over. Maybe this issue is solved by the
Fedora Legacy team for Red Hat Linux 9.