From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Weird behavior of crypt
Date: Fri, 29 Jan 2016 12:09:00 -0000 [thread overview]
Message-ID: <56AB4F64.3070807@gmail.com> (raw)
In-Reply-To: <CAFFOgCUoiL06QNFvXOJ-E46FOmpG4S_K4O52k+rt_Ysxpw2aag@mail.gmail.com>
On 29/01/2016 12:18, Alexandre Garnier wrote:
> Hello.
> I'm trying to do SHA-512 password encryption, but the result is really
> weird on Cygwin:
>
> # On Cygwin(either 32 or 64) 2.4.1-1, latest updates with crypt 1.1-1,
> libcrypt0 1.1-1, libcrypt-devel 1.1-1
> $ crypt '$6$7dl4B0fKUimdnR$' test_value
> $6wOs/zKP2jDM
>
> $ python -c 'import crypt; print crypt.crypt("test_value",
> "$6$7dl4B0fKUimdnR$")' # Python 2.7.10
> $6wOs/zKP2jDM
>
> $ perl -e 'print crypt("test_value", "\$6\$7dl4B0fKUimdnR\$")."\n"' #
> Perl v5.22.1
> $6wOs/zKP2jDM
>
> Am I missing something?
>
> On other system, I get a more expected result:
>
> # On Ubuntu 15.04
> $ mkpasswd --method=SHA-512 test_value 7dl4B0fKUimdnR
> $6$7dl4B0fKUimdnR$f6gCu.3IfrxhsnJKFnusDH.UudC.lLOSB1G3D1bIboWxlixzBy2xO/3rCKHmzfwekCTvmQd11bPdcsJOaLkCJ.
>
Not SHA-512, see
/usr/share/doc/crypt/crypt.README
This is the DES-crypt package Version 1.1
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)
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().
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-01-29 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 12:03 Alexandre Garnier
2016-01-29 12:09 ` Marco Atzeri [this message]
2016-01-29 14:00 ` Ismail Donmez
2016-01-29 14:44 ` Corinna Vinschen
2016-01-29 15:19 ` Alexandre Garnier
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=56AB4F64.3070807@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).