From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH crypt 5/8] Disable blowfish cipher
Date: Fri, 04 Aug 2017 08:32:00 -0000 [thread overview]
Message-ID: <7264180c-d075-c1aa-4776-bdc0c24f269f@cygwin.com> (raw)
In-Reply-To: <20170804074607.GK25551@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 305 bytes --]
On 2017-08-04 02:46, Corinna Vinschen wrote:
> Any details? I don't see anything target dependent in the blowfish
> code.
When I tested the various algorithms, all I got from blowfish was "*",
which indicates something went wrong. I'm still not sure what the issue
actually is.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2017-08-04 8:32 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 3/8] Export crypt_r 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:58 ` [PATCH crypt 8/8] Add .gitignore Yaakov Selkowitz
2017-08-04 2:58 ` [PATCH crypt 7/8] Update README Yaakov Selkowitz
2017-08-04 2:58 ` [PATCH crypt 4/8] Guard GNU extensions in header, declare other functions 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 [this message]
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=7264180c-d075-c1aa-4776-bdc0c24f269f@cygwin.com \
--to=yselkowitz@cygwin.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).