linux-kernel - Re: [PATCH v2] crypto: add self-tests for rfc4309(ccm(aes))

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090414111325.GA14305@hmsreliant.think-freely.org>
Date:	Tue, 14 Apr 2009 07:13:25 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Jarod Wilson <jarod@...hat.com>
Cc:	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
	Herbert Xu <herbert.xu@...hat.com>
Subject: Re: [PATCH v2] crypto: add self-tests for rfc4309(ccm(aes))

On Mon, Apr 13, 2009 at 07:11:00PM -0400, Jarod Wilson wrote:
> One more time, with feeling. Investigated using test vectors from rfc3610, but
> they all use a 13-byte nonce, we only support 11-byte, so I'm sticking with
> using the samples from a fips cavs example file I have on hand.
> 
> I swear I tested the first version of the patch before submitting last time,
> but upon further testing, don't know how it actually managed to run
> correctly w/o some of the additional changes in this version.
> 
> This version contains the same vectors, but some of them had incorrect klen's
> in them last time. Additionally, null input and associated data should be
> handled more appropriately, as well as the expected decryption verification
> failure vectors.
> 
> This version of the patch has been tested on both 2.6.30-rc1-git5 +
> cryptodev-2.6 and a Red Hat Enterprise Linux 5.x kernel, with some
> extra debugging spew added to verify it really *is* working.
> 
> Signed-off-by: Jarod Wilson <jarod@...hat.com>
> 
Acked-by: Neil Horman <nhorman@...driver.com>

> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/