Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix spelling of SUSE #5

Merged
merged 1 commit into from
May 22, 2018
Merged

Fix spelling of SUSE #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Makefile.am
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ crypt.h: crypt-base.h gen-crypt-h.awk config.h
$(AM_V_at)mv -f crypt.h.T crypt.h

# When we are being binary compatible, also install symbolic links to
# mimic SuSE's libowcrypt; any program that uses -lowcrypt in its
# mimic SUSE's libowcrypt; any program that uses -lowcrypt in its
# build, or already has a NEEDED entry for libowcrypt.so.1, will be
# redirected to libcrypt. The OW_CRYPT_1.0 symbol versions are already
# present in libcrypt.so.1.
Expand All @@ -80,7 +80,7 @@ crypt.h: crypt-base.h gen-crypt-h.awk config.h
# libraries involved, libcrypt.so.1 and libowcrypt.so.1. (We should
# be able to get away with this because in any circumstance where the
# soname of libcrypt isn't libcrypt.so.1, ENABLE_OBSOLETE_API should
# be automatically turned off, and as best I can tell, SuSE only ever
# be automatically turned off, and as best I can tell, SUSE only ever
# shipped libowcrypt.so.1.)
if ENABLE_OBSOLETE_API
if ENABLE_STATIC
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ libcrypt.so.1. We have taken pains to provide exactly the same
"symbol versions" as were used by glibc on various CPU architectures,
and to account for the variety of ways in which the Openwall
extensions were patched into glibc's libcrypt by some Linux
distributions. (For instance, compatibility symlinks for SuSE's
distributions. (For instance, compatibility symlinks for SUSE's
"libowcrypt" are provided.)

However, the converse is not true: programs linked against libxcrypt
Expand Down
2 changes: 1 addition & 1 deletion libcrypt.map.in
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ crypt XCRYPT_2.0 GLIBC_2.0
crypt_r XCRYPT_2.0 GLIBC_2.0

# Actively supported Openwall extensions; never actually added to
# upstream GNU libc, but present in at least Openwall, ALT, and SuSE
# upstream GNU libc, but present in at least Openwall, ALT, and SUSE
# Linux distributions with one or more of these symbol versions
crypt_rn XCRYPT_2.0 GLIBC_2.0 GLIBC_2.2.1
crypt_gensalt XCRYPT_2.0 GLIBC_2.0 GLIBC_2.2.1 OW_CRYPT_1.0
Expand Down