[opensuse-factory] Owl TCB patch uniq to suse and ASP linux glibc? Why? Are the GLIBC incompat symbols necessary?
* Both archives also include the Owl tcb patch updated to apply after the corresponding crypt_blowfish support patch. Unfortunately, the documentation updates found in Owl have been dropped from this quick and dirty update of the patches. * Forward ports of the patches from Owl to shadow-4.0.12 by Vincent Danen crypt_blowfish is fully integrated into Owl, distributions by ALT Linux team, and Annvix as the default password hashing scheme. It is part of the glibc package on SUSE Linux and ASPLinux. ^^^^^^^^^^ Part of the reasoning for forcing various incompatible changes has been because everyone else is doing it -- just to note, that doesn't seem to be the case here. What is the Owl TCB patch and why was it included in SUSE and why did it define a uniq symbol that gets required by all the binaries built with it (so you can't upgrade to a newer glibc that doesn't have these special additions ... I'm not sure how much I care if I have blowfish or such, over the other crypt mechanisms..... at least not if it means my software portability is easily damaged... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (1)
-
Linda Walsh