From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Tzvi Chumash <tzvi@research.att.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: blowfish from openSSL to kernel cryptoAPI
Date: Tue, 03 May 2011 17:48:13 +0300 [thread overview]
Message-ID: <4DC015AD.BA46DC3F@users.sourceforge.net> (raw)
In-Reply-To: ipnbl5$ug4$1@dough.gmane.org
Tzvi Chumash wrote:
> I'm trying (without much success) to decrypt in-kernel
> (2.6.18-194.el5PAE) a cipher that was created using openSSL
> (0.9.8e-fips-rhel5) using blowfish with a 56-byte key/8-byte iv. Are the
> implementations incompatible (i.e. can't encrypt in one and decrypt in
> the other?) or am I doing something wrong?
Check byte order of the two implementations. Many blowfish implementations
got byte order wrong. Does it help if you swap byte order from
0-1-2-3-4-5-6-7 to 7-6-5-4-3-2-1-0 of key/data/IV before and after crypto
operation?
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next prev parent reply other threads:[~2011-05-03 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 22:34 blowfish from openSSL to kernel cryptoAPI Tzvi Chumash
2011-05-03 14:48 ` Jari Ruusu [this message]
2011-05-03 15:46 ` Tzvi Chumash
2011-05-03 16:19 ` Emanuele Cesena
2011-05-03 17:37 ` Tzvi Chumash
2011-05-04 22:45 ` Herbert Xu
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=4DC015AD.BA46DC3F@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-crypto@vger.kernel.org \
--cc=tzvi@research.att.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.