nettle-bugs

nettle-bugs@lists.lysator.liu.se

2191 discussions

Re: [PATCH] build: add --enable-static option
by nisse＠lysator.liu.se 15 Dec '12

15 Dec '12

Alon Bar-Lev <alon.barlev(a)gmail.com> writes: > Working, thanks! Thanks for testing. ---disable-static checked in now. > BTW: > There is an issue with: > $ ./configure > $ make install DESTDIR=/tmp/xxx Skipping make is not currently supported. I.e., you're supposed to do $ ./configure $ make $ make install or even better $ ./configure $ make $ make check && make install Maybe a make install without a previous make all should be supported? Nevertheless, I guess the reported problem is a bug in tools/Makefile.in, the rule $(getopt_OBJS): ( cd .. && $(MAKE) $@ ) Does it work to replace $@ by `basename $@` ? (I haven't thought this through, maybe there's some better way to do it...) Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Some news for the next year
by nisse＠lysator.liu.se 15 Dec '12

15 Dec '12

The first item is a personal one. From January 7, I'll start working for Southpole Consulting AB, a small Sockholm-based consulting company mainly doing embedded (GNU/)Linux development. Second item is more directly related to Nettle. I will get funding from Internetfonden, for "Adapting GNU Nettle for embedded systems". This will mean two things: Support for elliptic curve signatures (and possibly some other ECC-related things), and optimizations for the ARM architecture. The funding is for 420 hours of work, most of which will be spent during the spring, and the project will be carried out under the umbrella of Southpole Consulting. A question for the list: Which variants of the ARM family are most important for Nettle applications? I'm not yet very familiar with the ARM world, but the following are some alternatives for testing and benchmarking: * The current most high-end processor, Cortex-A15, where an affordable development system seems to be a recent "chromebook". Not sure exactly which model, but I guess it's this one: http://www.amazon.co.uk/Samsung-Chromebook-Wifi-Latest-Model/dp/B009RF0AQ8/… * The previous "most high-end" processor, Cortex-A9. An affordable development system is the PandaBoard. http://www.omappedia.com/wiki/PandaBoard_FAQ * The Raspberry Pi computer, featuring an older (obsolete?) ARM1176JFZ, "ARMv6" architecture. http://www.raspberrypi.org/faqs * The low-end Cortex-M0, competing with less than $1 microcontrollers. Also "ARMv6" architecture. An affordable development system seems to be LPCXPRESSO board. http://www.embeddedartists.com/products/lpcxpresso/lpc11U14_xpr.php And if anybody here has some interesting ARM hardware to donate to the project, this is the right time. Best regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

3 5

Re: [PATCH] Probe for archiver tool
by nisse＠lysator.liu.se 15 Dec '12

15 Dec '12

Comitted now. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Re: [PATCH] build: add --enable-static option
by nisse＠lysator.liu.se 15 Dec '12

15 Dec '12

Alon Bar-Lev <alon.barlev(a)gmail.com> writes: > Gentoo bug#405525, support not installing static libraries. Can you check if the following, simpler, patch to Makefile.in does the job (still depends on IF_STATIC, from configure, of course)? It will use the install-static and uninstall-static targets unconditionally, but they won't do anything when LIBTARGETS is empty. Regards, /Niels diff --git a/Makefile.in b/Makefile.in index c63465c..d6be465 100644 --- a/Makefile.in +++ b/Makefile.in @@ -20,8 +20,8 @@ include config.make PRE_CPPFLAGS = -I. # FIXME: Add configuration of LIBEXT? -LIBTARGETS = libnettle.a @IF_HOGWEED@ libhogweed.a -SHLIBTARGETS = $(LIBNETTLE_FORLINK) @IF_HOGWEED@ $(LIBHOGWEED_FORLINK) +LIBTARGETS = @IF_STATIC@ libnettle.a @IF_HOGWEED@ libhogweed.a +SHLIBTARGETS = @IF_SHARED@ $(LIBNETTLE_FORLINK) @IF_HOGWEED@ $(LIBHOGWEED_FORLINK) getopt_SOURCES = getopt.c getopt1.c getopt_TARGETS = $(getopt_SOURCES:.c=.$(OBJEXT)) @@ -32,7 +32,7 @@ internal_TARGETS = $(internal_SOURCES:.c=.$(OBJEXT)) TARGETS = aesdata$(EXEEXT) desdata$(EXEEXT) twofishdata$(EXEEXT) \ shadata$(EXEEXT) gcmdata$(EXEEXT) \ $(getopt_TARGETS) $(internal_TARGETS) \ - $(LIBTARGETS) @IF_SHARED@ $(SHLIBTARGETS) + $(LIBTARGETS) $(SHLIBTARGETS) IMPLICIT_TARGETS = @IF_DLL@ $(LIBNETTLE_FILE) $(LIBHOGWEED_FILE) DOCTARGETS = @IF_DOCUMENTATION@ nettle.info nettle.html nettle.pdf -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Re: [PATCH] build: add --enable-static option
by nisse＠lysator.liu.se 15 Dec '12

15 Dec '12

Alon Bar-Lev <alon.barlev(a)gmail.com> writes: Thanks. I have one comment on the patch. > --- a/Makefile.in > +++ b/Makefile.in > @@ -21,7 +21,11 @@ include config.make > PRE_CPPFLAGS = -I. > # FIXME: Add configuration of LIBEXT? > LIBTARGETS = libnettle.a @IF_HOGWEED@ libhogweed.a > -SHLIBTARGETS = $(LIBNETTLE_FORLINK) @IF_HOGWEED@ $(LIBHOGWEED_FORLINK) > +@IF_STATIC@INSTALL_LIBTARGETS = install-static > +@IF_STATIC@UNINSTALL_LIBTARGETS = uninstall-static > +@IF_SHARED@SHLIBTARGETS = $(LIBNETTLE_FORLINK) @IF_HOGWEED@ $(LIBHOGWEED_FORLINK) > +@IF_SHARED@INSTALL_SHLIBTARGETS = install-shared-nettle @IF_HOGWEED@ install-shared-hogweed > +@IF_SHARED@UNINSTALL_SHLIBTARGETS = uninstall-shared I think I'd prefer to make the definitions unconditional, but with conditional values. E.g. UNINSTALL_SHLIBTARGETS = @IF_SHARED@ uninstall-shared rather than @IF_SHARED@UNINSTALL_SHLIBTARGETS = uninstall-shared Is there any reason that won't work? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

sha3 optimization
by nisse＠lysator.liu.se 13 Dec '12

13 Dec '12

I've spent the evening on optimizing sha3. I've written a first basic x86_64 implementation of sha3_permute, using 128-bit sse2 operations where practical, which gave a 30% speedup. And after working with the algorithm for a bit, I realized that it's fairly easy to reduce the number of passes each round makes over the data. So I tried that in the C implementation, and it gave a 20% speedup there. So now when I understand the algorithm better, I guess I'll have to rewrite the x86_64 implementation to reduce the number of passes there too. Still pretty slow, with sha3-256 at 32 cycles per byte at best. Which is far behind the claimed performance of 6-7 cycles/byte on x86_64 (close to the performance of sha1). I guess I should also have a look at that code (or does aybody on the list know which tricks are relevant?). The internal state is a 5x5 matrix of 64-bit words. If represented using 128-bit xmm registers, each row fits in two xmm registers and one regular 64-bit register. The steps which seem hardest to fit with 128-bit instructions is the permutation and rotation steps, which appear to want to treat 64-bit words individually. The current code (both C and assembly) keeps the state in memory, using double buffering, and doesn't try to fit more than one row at a time in registers. Keeping more of the state in registers is highly desirable. See http://git.lysator.liu.se/nettle/nettle/blobs/master/sha3-permute.c and http://git.lysator.liu.se/nettle/nettle/blobs/master/x86_64/sha3-permute.asm Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

2 2

SHA2 renaming
by nisse＠lysator.liu.se 03 Dec '12

03 Dec '12

With support for SHA3, it seems clear that nettle's naming for sha2 functions was a mistake. It should be "sha2_256", rather than "sha256". This is my current plan. Step 1 is as backwards compatible as practical, while step 2, to be taken at some later time, drops backwards compatibility. Step 1: * Split sha.h into sha1.h and sha2.h, and use the new names in sha2.h. Except for the name mangling, e.g., #define sha2_256_init nettle_sha256_init not #define sha2_256_init nettle_sha2_256_init in order to maintain ABI compatibility. * Keep sha.h for backwards compatibility. Have it include sha1.h and sha2.h, and use #define to make old names aliases for the new names. * Do a thorough rename in the implementation; use new names for all internal use of sha2, rename files, etc. * For all other interfaces where a sha2 function shows up in a name, e.g., hmac_sha256_set_key, and DSA_SHA256_MIN_P_BITS, rename for consistency and use #defines to make old names aliases. * For nettle_hash, make the new name of the struct an alias for the old, e.g., #define nettle_sha2_256 nettle_sha256 but for now do *not* change the contents of the name. I.e., nettle_sha2_256.name will still contain the string "sha256", not "sha2_256". Step 2: * Delete sha.h, and the other compatibility aliases defined elsewhere. * Do the rename also on library symbols, i.e., nettle_sha256_init -> nettle_sha2_256_init. * Change the value of the name fields of the nettle_hash objects. As far as I see, Step 1 maintains reasonably complete API and ABI compatibility. The only subtlety I'm aware of is C++ ABI compatibility for code *using* nettle, where I think struct sha256_ctx; vs struct sha2_256_ctx; #define sha256_ctx sha2_256_ctx would give different name mangling of C++ functions using arguments of this type (and not declared extern "C"). I think that is a problem that I'm going to ignore. Or do you think it is important enough to make the aliases for the struct tags the other way around? Comments? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

3 8

PBKDF2-HMAC-SHA512 test cases
by Fredrik Thulin 28 Nov '12

28 Nov '12

>From another thread : On Tue, 2012-11-27 at 22:47 +0100, Niels Möller wrote: ... > For lack of more authoritative test vectors, adding a couple of > testvectors generated by python-pbkdf2, to the nettle testsuite would > be nice. Attached is a patch that tries to validate the Nettle PBKDF2-HMAC-SHA512 implementation with a few values generated with python-pbkdf2 from https://www.dlitz.net/software/python-pbkdf2/. I also conducted 300,000 semi-random tests comparing the Nettle digest with corresponding OpenSSL digests, using QuickCheck-like testing, with good results. I did not use python-pbkdf2 checks for these, because frankly they were too slow. In case anyone is interested, I'm attaching the QC test too. Quick instructions for that one would be to install 'qc' from git://github.com/dbravender/qc.git, my python-ndnkdf from https://github.com/fredrikt/python-ndnkdf and then do $ nosetests -d qc-test.py /Fredrik

2 1

Salsa20/8 and Salsa20/12
by Simon Josefsson 28 Nov '12

28 Nov '12

I quickly discovered that I needed the round-reduced variants of Salsa20. Here they are. I didn't update the assembler part, so I would need help finishing that part. /Simon

3 17

Fast PBKDF2 in Python, using Nettle
by Fredrik Thulin 28 Nov '12

28 Nov '12

Hi I just published a module used in some PBKDF2-HMAC-SHA512 testing I've been doing under a contract with NORDUnet A/S. https://github.com/fredrikt/python-ndnkdf I invoke the new PBKDF2 functions in libnettle using Python ctypes, which achieves a ~ 25x speedup compared to the standard python-pbkdf2 that uses SHA512 from hashlib (presumably a C function), but does the xoring in native Python. PBKDF2-HMAC-SHA512 benchmark result : N= 16 -> Python == 0 ms, Nettle == 0 ms N= 32 -> Python == 1 ms, Nettle == 0 ms N= 64 -> Python == 2 ms, Nettle == 0 ms N= 128 -> Python == 4 ms, Nettle == 0 ms N= 256 -> Python == 8 ms, Nettle == 0 ms N= 512 -> Python == 18 ms, Nettle == 0 ms N= 1024 -> Python == 35 ms, Nettle == 1 ms N= 2048 -> Python == 68 ms, Nettle == 2 ms N= 4096 -> Python == 133 ms, Nettle == 5 ms N= 8192 -> Python == 262 ms, Nettle == 11 ms N= 16384 -> Python == 521 ms, Nettle == 22 ms If someone has access to a modern AMD CPU, I would be very interested in getting the benchmark output of examples/pbkdf2-plot on that machine. Thanks. /Fredrik

2 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

nettle-bugs