From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: mcrypt issue
Date: Mon, 16 Jul 2012 20:16:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A700145F9@USA7109MB022.na.xerox.net> (raw)
I am seeing an mcrypt problem with short plaintext strings.
I don't have a Linux box to compare results, so I don't
know if this is an upstream or a Cygwin issue.
$ mcrypt --version
Mcrypt v.2.6.8 (i686-pc-cygwin)
Linked against libmcrypt v.2.5.8
Copyright (C) 1998-2002 Nikos Mavroyanopoulos (nmav@gnutls.org)
$
Longer strings seem to work:
$ echo abcdef | mcrypt -q -k xyz | mcrypt -dq -k xyz
abcdef
$
But shorter ones not so much:
$ echo abcde | mcrypt -q -k xyz | mcrypt -dq -k xyz
ab▒$
--Ken Nellis
--
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 reply other threads:[~2012-07-16 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 20:16 Nellis, Kenneth [this message]
2012-07-16 22:06 ` Aaron Schneider
2012-07-18 15:26 ` Nellis, Kenneth
2012-07-18 19:10 ` Aaron Schneider
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=0D835E9B9CD07F40A48423F80D3B5A700145F9@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@xerox.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).