linux-kernel - [PATCH 0/8] DRBG: efficiency patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <7044529.FG2KhbPc9P@myon.chronox.de>
Date:	Sun, 17 Aug 2014 17:37:04 +0200
From:	Stephan Mueller <smueller@...onox.de>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org
Subject: [PATCH 0/8] DRBG: efficiency patches

Hi,

The following patch set contains random fixes to increase the efficiency of
the DRBG. Changes include the removal of unneeded memset(0) and sanity
checks. All changes do not weaken the implementation as only code is
removed that is clearly covered by other code paths.

In addition, the cpu_to_be kernel function together with a type cast is
used to convert an integer into its string representation. This patch
increases the speed of the DRBG by 10%.

Stephan Mueller (8):
  DRBG: replace int2byte with cpu_to_be
  DRBG: kzfree does not need a check for NULL pointer
  DRBG: remove superflowous checks
  DRBG: remove superflowous memset(0)
  DRBG: use kmalloc instead of kzalloc for V and C
  DRBG: remove unnecessary sanity checks
  DRBG: remove configuration of fixed values
  DRBG: remove unnecessary sanity check for shadow state

 crypto/drbg.c         | 130 ++++++++++++++++----------------------------------
 include/crypto/drbg.h |  19 +++-----
 2 files changed, 46 insertions(+), 103 deletions(-)

-- 
1.9.3


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/