From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 4/4] add options for recently added SHA256 and SHA512 hashes
Date: Tue, 26 Mar 2013 14:05:25 +0100 [thread overview]
Message-ID: <1364303125-4866-5-git-send-email-post@lespocky.de> (raw)
In-Reply-To: <1364303125-4866-1-git-send-email-post@lespocky.de>
Make new hash functions available through ptxdist config menu.
Signed-off-by: Alexander Dahl <post@lespocky.de>
---
rules/dropbear.in | 26 ++++++++++++++++++++++++++
rules/dropbear.make | 16 ++++++++++++++++
2 files changed, 42 insertions(+), 0 deletions(-)
diff --git a/rules/dropbear.in b/rules/dropbear.in
index 8c878ec..21301ba 100644
--- a/rules/dropbear.in
+++ b/rules/dropbear.in
@@ -232,6 +232,32 @@ config DROPBEAR_SHA1_96
Although slower than MD5, this larger digest size makes it
stronger against brute force attacks.
+config DROPBEAR_SHA256
+ bool
+ prompt "sha256"
+ default n
+ help
+ SHA-2 is a set of cryptographic hash functions (SHA-224, SHA-256,
+ SHA-384, SHA-512) designed by the National Security Agency (NSA)
+ and published in 2001 by the NIST as a U.S. Federal Information
+ Processing Standard. SHA stands for Secure Hash Algorithm. SHA-2
+ includes a significant number of changes from its predecessor,
+ SHA-1. SHA-2 consists of a set of four hash functions with digests
+ that are 224, 256, 384 or 512 bits.
+
+config DROPBEAR_SHA512
+ bool
+ prompt "sha512"
+ default n
+ help
+ SHA-2 is a set of cryptographic hash functions (SHA-224, SHA-256,
+ SHA-384, SHA-512) designed by the National Security Agency (NSA)
+ and published in 2001 by the NIST as a U.S. Federal Information
+ Processing Standard. SHA stands for Secure Hash Algorithm. SHA-2
+ includes a significant number of changes from its predecessor,
+ SHA-1. SHA-2 consists of a set of four hash functions with digests
+ that are 224, 256, 384 or 512 bits.
+
config DROPBEAR_MD5
bool
prompt "md5"
diff --git a/rules/dropbear.make b/rules/dropbear.make
index 2beb7ef..74f273f 100644
--- a/rules/dropbear.make
+++ b/rules/dropbear.make
@@ -181,6 +181,22 @@ else
@$(call disable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_SHA1_96_HMAC)
endif
+ifdef PTXCONF_DROPBEAR_SHA256
+ @echo "ptxdist: enabling sha256"
+ @$(call enable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_SHA2_256_HMAC)
+else
+ @echo "ptxdist: disabling sha256"
+ @$(call disable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_SHA2_256_HMAC)
+endif
+
+ifdef PTXCONF_DROPBEAR_SHA512
+ @echo "ptxdist: enabling sha512"
+ @$(call enable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_SHA2_512_HMAC)
+else
+ @echo "ptxdist: disabling sha512"
+ @$(call disable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_SHA2_512_HMAC)
+endif
+
ifdef PTXCONF_DROPBEAR_MD5
@echo "ptxdist: enabling md5"
@$(call enable_c, $(DROPBEAR_DIR)/options.h,DROPBEAR_MD5_HMAC)
--
1.7.2.5
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-03-26 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 13:05 [ptxdist] dropbear: fixing some stuff, version bump, new hashes Alexander Dahl
2013-03-26 13:05 ` [ptxdist] [PATCH 1/4] remove long gone options Alexander Dahl
2013-03-26 13:05 ` [ptxdist] [PATCH 2/4] fix renamed macros Alexander Dahl
2013-03-26 13:05 ` [ptxdist] [PATCH 3/4] bump upstream version and recreate patch series Alexander Dahl
2013-03-26 13:05 ` Alexander Dahl [this message]
2013-03-27 18:21 ` [ptxdist] dropbear: fixing some stuff, version bump, new hashes Michael Olbrich
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=1364303125-4866-5-git-send-email-post@lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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