mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Trent Piepho <tpiepho@kymetacorp.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH v2 2/3] crypto: add RSA support
Date: Fri, 8 Jan 2016 08:47:56 +0100	[thread overview]
Message-ID: <20160108074756.GY13058@pengutronix.de> (raw)
In-Reply-To: <1452204201.4474.115.camel@rtred1test09.kymeta.local>

On Thu, Jan 07, 2016 at 10:03:10PM +0000, Trent Piepho wrote:
> On Wed, 2016-01-06 at 18:01 +0100, Marc Kleine-Budde wrote:
> > +
> > +static void rsa_convert_big_endian(uint32_t *dst, const uint32_t *src, int len)
> > +{
> > +	int i;
> > +
> > +	for (i = 0; i < len; i++)
> > +		dst[i] = fdt32_to_cpu(src[len - 1 - i]);
> > +}
> > +
> 
> 
> > +struct rsa_public_key {
> > +	uint len;		/* len of modulus[] in number of uint32_t */
> > +	uint32_t n0inv;		/* -1 / modulus[0] mod 2^32 */
> > +	uint32_t *modulus;	/* modulus as little endian array */
> > +	uint32_t *rr;		/* R^2 as little endian array */
> > +	uint64_t exponent;	/* public exponent */
> 
> This says little endian, but it looks like it's really CPU endian, i.e.
> on a big endian system it would be big endian.

Indeed the original author of this code must have assumed that big
endian systems do not exist. Here's another one:

> +     /* Convert from big endian byte array to little endian word array. */
> +     for (i = 0, ptr = inout + key->len - 1; i < key->len; i++, ptr--)
> +             val[i] = get_unaligned_be32(ptr);

It "little endian" comments should be replaced by "cpu endian" in the
comments.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-01-08  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 17:01 [PATCH v2 0/3] FIT Support Marc Kleine-Budde
2016-01-06 17:01 ` [PATCH v2 1/3] crypto: add digest_alloc_by_algo() Marc Kleine-Budde
2016-01-06 17:01 ` [PATCH v2 2/3] crypto: add RSA support Marc Kleine-Budde
2016-01-07 22:03   ` Trent Piepho
2016-01-08  7:47     ` Sascha Hauer [this message]
2016-01-06 17:01 ` [PATCH v2 3/3] bootm: add initial FIT support Marc Kleine-Budde
2016-01-11  9:19   ` Sascha Hauer

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=20160108074756.GY13058@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=kernel@pengutronix.de \
    --cc=tpiepho@kymetacorp.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