From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gnupg: Add options for SHA-256 and SHA-512 hashes
Date: Thu, 6 Apr 2017 07:01:21 +0300 [thread overview]
Message-ID: <20170406040121.5ptco5esekcyrxlu@tarshish> (raw)
In-Reply-To: <20170406010908.95234-1-jack@kumunetworks.com>
Hi Jack,
On Wed, Apr 05, 2017 at 06:09:08PM -0700, Jack Breese wrote:
> Signed-off-by: Jack Breese <jack@kumunetworks.com>
> ---
> package/gnupg/Config.in | 10 ++++++++++
> package/gnupg/gnupg.mk | 12 ++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/package/gnupg/Config.in b/package/gnupg/Config.in
> index 30f215fed..87b3afe76 100644
> --- a/package/gnupg/Config.in
> +++ b/package/gnupg/Config.in
> @@ -26,6 +26,16 @@ config BR2_PACKAGE_GNUPG_RSA
> help
> Support for RSA public key algorithm
>
> +config BR2_PACKAGE_GNUPG_SHA256
> + bool "SHA256 support"
> + help
> + Support for SHA256 hash algorithm
> +
> +config BR2_PACKAGE_GNUPG_SHA512
> + bool "SHA512 support"
> + help
> + Support for SHA512 hash algorithm
What is the size impact of these options? In case the size increase is
relatively small just enable them unconditionally. I'd say that, given the
security implications, we should enable SHA2 even if the size impact is big.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2017-04-06 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 1:09 [Buildroot] [PATCH 1/1] gnupg: Add options for SHA-256 and SHA-512 hashes Jack Breese
2017-04-06 4:01 ` Baruch Siach [this message]
2017-04-07 0:44 ` Jack Breese
2017-04-07 1:09 ` [Buildroot] [PATCH v2] " Jack Breese
2017-04-08 13:32 ` Thomas Petazzoni
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=20170406040121.5ptco5esekcyrxlu@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.