linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Sassu <myrobmail@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Suspect bug in the authenc module
Date: Thu, 4 Mar 2010 11:54:05 +0100	[thread overview]
Message-ID: <201003041154.05369.myrobmail@gmail.com> (raw)
In-Reply-To: <20100301132433.GA20729@secunet.com>

Hello

i pulled the crypto-2.6 repo today. Issues appear to be solved for both 32-bit 
and 64-bit systems. Many thanks!

I have got another trouble when compiling my test module with a 64-bit 
operating system:

when dumping the data placed pointed by the scatterlist array i noted that the 
assoc is always zero'ed. I investigated further and it seems that the problem 
is the static allocation of the assoc string in my test module. When using the 
kmalloc the dump is correct.   

On Monday 01 March 2010 14:24:33 Steffen Klassert wrote:
> On Sat, Feb 27, 2010 at 12:14:15PM +0100, Roberto Sassu wrote:
> > Hello
> > 
> > i'm trying to use the authenc module and i wrote a small kernel module
> > that simply encrypts/decrypts a fixed data using the hmac(sha1) as
> > authentication algorithm and cbc(aes) as encryption algorithm.
> > The used platform is a KVM quest with Fedora 12 i686 and the latest
> > kernel 2.6.33.
> > I have taken the code from the testmgr and from net/ipv4/esp4.c.
> > But, when testing the code, attached in this mail, the
> > crypto_aead_decrypt() function always replies -EBADMSG.
> 
> I've posted two fixes for authenc to the linux-crypto list last week.
> Could you please try whether these patches fix your problems?
> 
> Thanks,
> 
> Steffen

  reply	other threads:[~2010-03-04 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 11:14 Suspect bug in the authenc module Roberto Sassu
2010-03-01 13:24 ` Steffen Klassert
2010-03-04 10:54   ` Roberto Sassu [this message]
2010-03-05  7:26     ` 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=201003041154.05369.myrobmail@gmail.com \
    --to=myrobmail@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=steffen.klassert@secunet.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 NNTP newsgroup(s).