Feature changed by: Andreas Schwab (zxyyz)
Feature #314945, revision 17
Title: No ABI extension in glibc
- openSUSE Distribution: Evaluation by engineering manager
+ openSUSE Distribution: Done
Requested by: Andreas Jaeger (a_jaeger)
Partner organization: openSUSE.org
Currently we have the crypt-blowfish patches in glibc that add new
symbol versions to it. I consider that addition wrong and propose to
find a solution (might be getting the support in upstream, or using a
separate library,...) that does not extend the ABI at all.
The goal should be that our glibc exports exactly the same symbols as
upstream glibc does.
#1: Thorsten Kukuk (kukuk) (2013-04-02 11:10:27)
The answer is simple: remove them. We only need to remove one patch
from Ludwig from pam-modules, which I did never integrate upstream
since I always said that it is wrong.
But I don't know what else Ludwig did modify for this.
#2: Ludwig Nussel (lnussel) (2013-04-02 13:20:47) (reply to #1)
It affected mostly projects of yours that duplicated the code.
Fortunately pwdutils is gone and pam_unix2 is irrelevant now. What's
left is yast and IIRC whois. You can find out easily by checking the
repo meta data for the requirements.
Still, the solution is not to duplicate the code again in several
packages but to have it at a central place. glibc has crypt so it
should have crypt_gensalt as well. The patch should be upstreamed in
one way or another and in fact that was the intention to solve the
problem for everyone.
+ #11: Andreas Schwab (zxyyz) (2013-08-15 09:07:32)
+ Implemented in 13.1 and therefore also in SLE 12. Extra interfaces
+ moved to libowcrypt.