From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] nettle: The variable named p in the patch file was incorrectly named.
Date: Wed, 9 Mar 2016 02:03:11 +0100 [thread overview]
Message-ID: <56DF764F.204@opendreambox.org> (raw)
In-Reply-To: <1457473760-8486-1-git-send-email-nathangutzmann@gmail.com>
Hello Nathan,
On 08.03.2016 22:49, ngutzmann wrote:
> The variable in question should have been called ecc->p. The patch has been updated
> so that the compilation of the nettle recipe would complete successfully.
>
> Signed-off-by: ngutzmann <nathangutzmann@gmail.com>
> ---
> meta/recipes-support/nettle/nettle-2.7.1/CVE-2015-8803_8805.patch | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/nettle/nettle-2.7.1/CVE-2015-8803_8805.patch b/meta/recipes-support/nettle/nettle-2.7.1/CVE-2015-8803_8805.patch
> index 1c4b9a9..a956f42 100644
> --- a/meta/recipes-support/nettle/nettle-2.7.1/CVE-2015-8803_8805.patch
> +++ b/meta/recipes-support/nettle/nettle-2.7.1/CVE-2015-8803_8805.patch
> @@ -40,7 +40,7 @@ Index: nettle-2.7.1/ecc-256.c
> u1 -= cy;
> - u1 += cnd_add_n (t, rp + n - 4, ecc->p, 3);
> +
> -+ cy = cnd_add_n (t, rp + n - 4, p->m, 2);
> ++ cy = cnd_add_n (t, rp + n - 4, ecc->p, 2);
> + u0 += cy;
> + u1 += (u0 < cy);
> u1 -= (-t) & 0xffffffff;
>
looks good to me. However, I needed to lookup the commit where the
backport originated from, because the reason for exchanging m and p
isn't obvious at all without knowing the original commit. Maybe you
could include it in your commit message.
https://git.lysator.liu.se/nettle/nettle/commit/c71d2c9d20eeebb985e3872e4550137209e3ce4d
Regards,
Andreas
next prev parent reply other threads:[~2016-03-09 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 21:49 [meta-oe][PATCH] nettle: The variable named p in the patch file was incorrectly named ngutzmann
2016-03-09 1:03 ` Andreas Oberritter [this message]
2016-03-09 16:14 ` Nathan Gutzmann
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=56DF764F.204@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.