From: Oleg Makarenko <mole@quadra.ru>
To: linux-ppp@vger.kernel.org
Subject: Re: [pptp-devel] Re: [2/2]: ppp_mppe inclusion
Date: Tue, 31 Aug 2004 22:23:46 +0000 [thread overview]
Message-ID: <4134FA72.2020107@quadra.ru> (raw)
In-Reply-To: <20040720204723.GC27576@lists.us.dell.com>
Matt Domsch wrote:
>On Mon, Aug 30, 2004 at 05:42:05PM -0500, Matt Domsch wrote:
>
>
>>On Fri, Jul 30, 2004 at 11:33:09PM +0400, Oleg Makarenko wrote:
>>
>>
>>>2. For some reason you can not use non GFP_KERNEL memory and scatter
>>>lists or at least mix them in crypto_digest(). That is why sha_pad is
>>>now in struct state {}.
>>>
>>>
>
>Can you describe what happens when you do?
>
>
>
>
It didn't crash/panic and everything seems to work fine but the digest
was incorrect.
When I'd looked at the actual data that were passed to sha1_update() I
saw all FF's instead of 00's (or F2's) for pad1 (pad2).
The only difference was the memory type and to verify that that is the
reason for wrong calculated hash value (and only as a workaround) I've
placed pads to struct state. Struct state is already gfp_kernel so there
were no need to bother with malloc/free :)
Actually I don't know what is wrong here and what is the right way to
solve it. Is it by design or is it a bug in crypto?
It is easy to add one more test for sha1 using static memory and I hope
I'll be able to reproduce the problem.
I'll try tomorrow and let you know the results.
regards,
Oleg
next prev parent reply other threads:[~2004-08-31 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 20:47 [2/2]: ppp_mppe inclusion Matt Domsch
2004-07-30 19:33 ` Oleg Makarenko
2004-07-31 18:34 ` Matt Domsch
2004-08-30 22:42 ` [pptp-devel] " Matt Domsch
2004-08-30 22:48 ` Matt Domsch
2004-08-31 22:23 ` Oleg Makarenko [this message]
2004-09-05 18:23 ` Oleg Makarenko
2004-10-12 17:14 ` Matt Domsch
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=4134FA72.2020107@quadra.ru \
--to=mole@quadra.ru \
--cc=linux-ppp@vger.kernel.org \
/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 NNTP newsgroup(s).