From: Emanuele Cesena <emanuele.cesena@gmail.com>
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 18:19:25 +0200 [thread overview]
Message-ID: <1304439565.2652.47.camel@ec> (raw)
In-Reply-To: <ipp84b$m6s$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Tue, 2011-05-03 at 11:46 -0400, Tzvi Chumash wrote:
> I was assuming that given the same parameters (e.g. encryption
> algorithm, CBC, key, iv), the cipher data would be equivalent between
> different implementations (in this case openSSL/cryptoapi). Was that a
> wrong assumption?
>
It may be a stupid remark... anyway, OpenSSL uses key/iv "internally"
and exposes to the user passphrase and salt. Did you check that you have
not confused them?
Best,
--
Emanuele Cesena <emanuele.cesena@gmail.com>
Il corpo non ha ideali
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5998 bytes --]
next prev parent reply other threads:[~2011-05-03 16:20 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
2011-05-03 15:46 ` Tzvi Chumash
2011-05-03 16:19 ` Emanuele Cesena [this message]
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=1304439565.2652.47.camel@ec \
--to=emanuele.cesena@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox