From: Yaakov Selkowitz <yselkowi@redhat.com>
To: cygwin-apps@cygwin.com
Subject: [PATCH crypt 7/8] Update README
Date: Fri, 04 Aug 2017 02:58:00 -0000 [thread overview]
Message-ID: <20170804025258.19248-8-yselkowi@redhat.com> (raw)
In-Reply-To: <20170804025258.19248-1-yselkowi@redhat.com>
---
crypt.README | 38 ++++----------------------------------
1 file changed, 4 insertions(+), 34 deletions(-)
diff --git a/crypt.README b/crypt.README
index d7ee763..336737e 100644
--- a/crypt.README
+++ b/crypt.README
@@ -1,46 +1,16 @@
-This is the DES-crypt package Version 1.1
+This is the crypt package Version 2.0
It provides a static library libcrypt.a as well as a shared library
cygcrypt-0.dll together with a link lib libcrypt.dll.a, which export
the functions
crypt(3)
+ crypt_r(3)
encrypt(3)
setkey(3)
-The passwords created by crypt(3) are 56 bit DES encrypted and are
-100% identical to those created by the Linux crypt().
-
-Additionally, this package provides a command line tool crypt.exe
-which is a tool to generate encrypted passwords from cleartext
-passwords. The encrypted password is written to stdout with a trailing
-line feed.
-
-Use this tool to create password entries in /etc/passwd on 9x systems.
-On 9x machines, this DES password authentication is used in applications
-like e. g. login(1) or ftpd(8). Note that the password entry in
-/etc/passwd is not used on NT systems. Instead, users are authenticated
-using the NT password itself. So crypt.exe is mainly a convenience for
-9x users.
-
-Note that this tool does *not* provide the crypt(1) functionality known
-from e. g. SUN Solaris(tm) machines. The encryption used here is
-incompatible with the encryption used there.
-
-The usage of "our" crypt is like this:
-
-crypt cleartext
-
- generates a password with a random salt.
-
-crypt salt cleartext
-
- generates a password with salt `salt'. The result can be used to
- compare a given encrypted password with a cleartext password eg.
- typed by a user.
-
-The salt is a two character string which consists of the first two
-characters of the encrypted password.
+The passwords created by crypt(3) are 100% identical to those created by
+the Linux crypt(). DES, MD5, SHA-256, and SHA-512 algorithms are supported.
Please send requests, error reports etc. to the mailing list
cygwin@cygwin.com.
--
2.13.2
next prev parent reply other threads:[~2017-08-04 2:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 2:53 [PATCH crypt 0/8] Use musl implementation Yaakov Selkowitz
2017-08-04 2:53 ` [PATCH crypt 1/8] Import musl sources Yaakov Selkowitz
2017-08-04 2:53 ` [PATCH crypt 2/8] Port sources to Cygwin Yaakov Selkowitz
2017-08-04 2:53 ` [PATCH crypt 3/8] Export crypt_r Yaakov Selkowitz
2017-08-04 2:58 ` Yaakov Selkowitz [this message]
2017-08-04 2:58 ` [PATCH crypt 4/8] Guard GNU extensions in header, declare other functions Yaakov Selkowitz
2017-08-04 2:58 ` [PATCH crypt 8/8] Add .gitignore Yaakov Selkowitz
2017-08-04 3:01 ` [PATCH crypt 5/8] Disable blowfish cipher Yaakov Selkowitz
2017-08-04 7:46 ` Corinna Vinschen
2017-08-04 8:32 ` Yaakov Selkowitz
2017-09-01 1:38 ` Yaakov Selkowitz
2017-08-04 3:02 ` [PATCH crypt 6/8] Update Makefile Yaakov Selkowitz
2017-09-01 1:40 ` [PATCH v2 " Yaakov Selkowitz
2017-09-01 9:03 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170804025258.19248-8-yselkowi@redhat.com \
--to=yselkowi@redhat.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).