From: Stephan Mueller <smueller@chronox.de>
To: sri sowj <srisowj4linux@gmail.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: Counter Size in CTR mode for AES Driver
Date: Fri, 10 Apr 2015 22:51:11 +0200 [thread overview]
Message-ID: <3837185.yfoG22Ljkb@tachyon.chronox.de> (raw)
In-Reply-To: <CAHTT9V+VXHYMc1Nkc9hh0Ew7nZy28zTc=rip4op-+BvC80MsTw@mail.gmail.com>
Am Samstag, 11. April 2015, 00:30:30 schrieb sri sowj:
Hi sri,
> Hi All,
>
> I have seen multiple open source drivers for AES(CTR) mode for
> different Crypto Hardware Engines, I was not really sure on
> countersize,nonce etc.
> Please can any one provide some info on the following
>
> #1:How does AES driver identifies the counter size during the CTR mode
> of operation?
I am not sure about the question, but the block chaining mode is orthogonal to
the block cipher.
Thus, the block cipher does not need to know of the counter size of CTR. That
applies to any block chaining mode.
>
> looks like AES in CTR mode supports "countersize" of multiple lengths as
below:
> >>1: First is a counter which is made up of a nonce and counter. The nonce
> >>is random, and the remaining bytes are counter bytes (which are
> >>incremented).
> For example, a 16 byte block cipher might use the high 8 bytes as a
> nonce, and the low 8 bytes as a counter.
>
> >>2: Second is a counter block, where all bytes are counter bytes and can be
> >>incremented as carries are generated.
> For example, in a 16 byte block cipher, all 16 bytes are counter bytes
>
> #2: Does Linux Kernel Crypto subsystem increments the counter value
> for every block of input or is it needs tp be taken care by Kernel
> Driver for the respective Crypto H/W ?
This depends on your choice -- the kernel crypto API provides crypto_inc() for
the increment, it provides the ctr template to wrap a block chaining mode. The
kernel crypto API does not restrict, it enables you.
>
>
> #3:counters and nonces are something which will be extracted from the
> IV i.e., IV = nonce + counter
> Note if "l" is length of IV then first "l/2" is length of nonce and
> next "l/2" is length of counter.
What you describe may be on e convention. But the ctr.c template initializes
the counter value to 0 during init time. So, you see that there is no hard
fact. The counter is in fact just an IV.
>
> Any information regarding the above is really appreciable.
>
> BR,
> SriSowj
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ciao
Stephan
next prev parent reply other threads:[~2015-04-10 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 19:00 Counter Size in CTR mode for AES Driver sri sowj
2015-04-10 20:51 ` Stephan Mueller [this message]
2015-04-11 3:37 ` sri sowj
2015-04-11 20:42 ` Stephan Mueller
2015-04-11 15:40 ` Sandy Harris
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=3837185.yfoG22Ljkb@tachyon.chronox.de \
--to=smueller@chronox.de \
--cc=linux-crypto@vger.kernel.org \
--cc=srisowj4linux@gmail.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