Which was used on Ultrix and Tru64, only) widely used password hashingĪlgorithms, which before were specific to just some operating The crypt and gensalt functions are supporting all (except for Crypt16, Setkey, setkey_r, and fcrypt) cannot be compiled against libxcrypt. Also, programs that useĬertain legacy APIs supplied by glibc's libcrypt (encrypt, encrypt_r, Pioneered by Openwall Linux, crypt_rn, crypt_ra, crypt_gensalt,Ĭrypt_gensalt_rn, and crypt_gensalt_ra. It comes with a set of extended interfaces However, theĬonverse is not true: programs linked against libxcrypt will not work Glibc's libcrypt and does not require any rebuilds. Libxcrypt will be fully binary compatible with software linked against Oppinion about replacing glibc's libcrypt with libxcrypt for Fedora Separate project which can evolve quicker, I'd like to hear your Libcrypt from glibc in some time and splitting it out into a Since there has been some discussion in the last time about removing To the wiki, and if you want to take the review I'll gladly take one If that's the case, please RTFM me a link Been busy lately, I'm a littleīehind on anything Fedora. The package itself is simple, but it bundles javascript and doesn'tīuild on all main platforms so I may have to be granted an exceptionįrom some group starting with an F. Support, although I have cases where it would be relevant, but I don't Overhead, but so far I've been monitoring small single-threaded I came across kcov when I was looking for a way to measure codeĬoverage in a Rust project and I'm impressed. Instead of requiring compile-time instrumentation. Lcov, except that all it needs is a binary with DWARF debuginfo It has no relation to Linux's kcov and is more akin to I just submitted a review request for kcov that I recentlyĭiscovered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |