nettle-bugs

nettle-bugs@lists.lysator.liu.se

1 participants
2200 discussions

memxor
by Nikos Mavrogiannopoulos 14 Sep '11

14 Sep '11

On Tue, Sep 13, 2011 at 1:17 PM, Niels Möller <nisse(a)lysator.liu.se> wrote: > Then you shouldn't need to bother about the lsh directory again. You > have a symlink to the shared aclocal.m4 (and to some other shared > files). Ok I figured out. I attach a working SSE2 detection. > Thanks. I'll have to think some more on how to organize this. Some > properties I'd like to have: > 1. Don't require users to call any init function. > One could define memxor to jump via a function pointer, and have an > initial value for that pointer which jumps to the routine to set the > pointer to the right function, and then use it. Overwriting the > pointer should be atomic, so no locking needed even for multithreaded > programs. I don't think locking is an issue if you only call a function on initialization. You can expect (and require) that a library isn't going to be initialized by multiple threads. I don't know however of a portable way to do initialization transparently without an explicit function call. > 3. Avoid using gcc-specific things, including inline asm, in the C > source files. The cpuid test would have then to be moved to an assembly file. > Other obvious uses for cpu detection in nettle: > * The AES code could check for the special aes instructions. Indeed. Once a framework for overwriting functionality is set, those would be not very hard to add. However setting such framework in nettle seems to require substantial work as all exported functions need to be replaced by function pointers thus breaking ABI. If this is done gradually (it has to, as you never know what you would be able to optimize in a new processor) it would be worse, since every optimization added would break ABI. Maybe it makes sense to have a libgcrypt-like high level interface and optimizations would be used only there. The existing C api remains an API to access the C implementation. This could also address the problem with optimized hash algorithms[0], since most cpu-assisted sha1 or sha256 implementations work on an output=hash(data,length) basis and do not map to the existing API. [0]. http://www.mail-archive.com/openssl-dev@openssl.org/msg21787.html > * The serpent code can use %xmm and %ymm registers, when present. On > x86_64, as far as I'm aware all current implementations have sse2, > but one could check for, and make use of, the 256-bit %ymm > registers. I wouldn't care of serpent optimizations much :) regards, Nikos

2 3

memxor
by Nikos Mavrogiannopoulos 13 Sep '11

13 Sep '11

Hello, I've run some tests with memxor on a x86-64 machine. My results are: * C implementation (compiled with gcc 4.4): Xoring in chunks of 32768 bytes: done. 50.09 Gb in 5.00 secs: 10.02 Gb/sec Xoring (unaligned) in chunks of 32768 bytes: done. 39.90 Gb in 5.00 secs: 7.98 Gb/sec * ASM implementation: Xoring in chunks of 32768 bytes: done. 38.32 Gb in 5.00 secs: 7.66 Gb/sec Xoring (unaligned) in chunks of 32768 bytes: done. 30.16 Gb in 5.00 secs: 6.03 Gb/sec It seems that in x86-64 the ASM version is slower than the C one. Moreover I noticed that the loop unrolling techniques used in the C code have no visible performance benefit. However, an SSE2 version of memxor (attached) increases performance by 30% or more in the same CPU. * SSE2: Xoring in chunks of 32768 bytes: done. 69.94 Gb in 5.00 secs: 13.98 Gb/sec Xoring (unaligned) in chunks of 32768 bytes: done. 65.96 Gb in 5.00 secs: 13.19 Gb/sec regards, Nikos

2 8

ANNOUNCE: Nettle-2.4
by nisse＠lysator.liu.se 03 Sep '11

03 Sep '11

Due to a bug discovered in Nettle-2.3, released yesterday, I'm a bit embarrassed to announce a new release of GNU Nettle. Nettle is a low-level cryptographic library. Homepage at http://www.lysator.liu.se/~nisse/nettle/. NEWS for the 2.4 release This is a bugfix release only. It turned out ripemd160 in the 2.3 release was broken on all big-endian systems, due to a missing include of config.h. nettle-2.4 fixes this. The library is intended to be binary compatible with nettle-2.2 and nettle-2.3. The shared library names are libnettle.so.4.3 and libhogweed.so.2.1, with sonames still libnettle.so.4 and libhogweed.so.2. NEWS for the 2.3 release * Support for the ripemd-160 hash function. * Generates and installs nettle.pc and hogweed.pc files, for use with pkg-config. Feedback appreciated. For projects using autoconf, the traditional non-pkg-config ways of detecting libraries, and setting LIBS and LDFLAGS, is still recommended. * Fixed a bug which made the testsuite fail in the GCM test on certain platforms. Should not affect any documented features of the library. * Reorganization of the code for the various Merkle-Damgård hash functions. Some fields in the context structs for md4, md5 and sha1 have been renamed, for consistency. Applications should not peek inside these structs, and the ABI is unchanged. * In the manual, fixed mis-placed const in certain function prototypes. The library is intended to be binary compatible with nettle-2.2. The shared library names are libnettle.so.4.2 and libhogweed.so.2.1, with sonames still libnettle.so.4 and libhogweed.so.2. The latest version is available at http://www.lysator.liu.se/~nisse/archive/nettle-2.4.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-2.4.tar.gz ftp://ftp.gnu.org/gnu/nettle/nettle-2.4.tar.gz Happy hacking, /Niels möller -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

ANNOUNCE: Nettle-2.3
by nisse＠lysator.liu.se 03 Sep '11

03 Sep '11

I'm happy to announce a new version of GNU Nettle, a low-level cryptographics library. The Nettle home page can be found at http://www.lysator.liu.se/~nisse/nettle/. NEWS for the 2.3 release * Support for the ripemd-160 hash function. * Generates and installs nettle.pc and hogweed.pc files, for use with pkg-config. Feedback appreciated. For projects using autoconf, the traditional non-pkg-config ways of detecting libraries, and setting LIBS and LDFLAGS, is still recommended. * Fixed a bug which made the testsuite fail in the GCM test on certain platforms. Should not affect any documented features of the library. * Reorganization of the code for the various Merkle-Damgård hash functions. Some fields in the context structs for md4, md5 and sha1 have been renamed, for consistency. Applications should not peek inside these structs, and the ABI is unchanged. * In the manual, fixed mis-placed const in certain function prototypes. The library is intended to be binary compatible with nettle-2.2. The shared library names are libnettle.so.4.2 and libhogweed.so.2.1, with sonames still libnettle.so.4 and libhogweed.so.2. Available at http://www.lysator.liu.se/~nisse/archive/nettle-2.3.tar.gz and soon also at ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-2.3.tar.gz ftp://ftp.gnu.org/gnu/nettle/nettle-2.3.tar.gz Happy hacking, /Niels Möller -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 1

RIPEMD-160 Implementation
by Andres Mejia 01 Sep '11

01 Sep '11

Here's a patch that will implement RIPEMD-160 for nettle. It's code ported from libgcrypt. A reference to RIPEMD-160 is in the source. Also, this patch includes testcases and I followed what looked to me as nettle coding conventions. There's no documentation update in this patch. I didn't look into how documentation was generated in nettle. Also, this patch is against the nettle-2.2 release. I couldn't get the CVS snapshot of nettle building, particularly because of the integration of LSH. -- Regards, Andres Mejia

2 8

make in freebsd
by Nikos Mavrogiannopoulos 28 Aug '11

28 Aug '11

Hello, I tried to do a "./configure && make" in freebsd an got an error during make. If I use GNU make instead it works. I attach the error output from the make command and the generated Makefile. regards, Nikos

2 3

Re: RIPEMD-160 Implementation
by Nikos Mavrogiannopoulos 27 Aug '11

27 Aug '11

On 08/27/2011 09:05 PM, Niels Möller wrote: > Are any other variants of ripemd in use? (According to wikipedia, > there's original ripemd, ripemd-128, ripend-160, ripemd-256 and > ripemd-320, but I have no idea which of them are in use today or are > likely to be used in the future). ripemd and ripemd-128 are considered broken. I don't know if ripemd-x, x>=256 have been used anywhere. Having the SHA-3 winner instead would be a much better choice. regards, Nikos

2 2

Few Questions About Nettle Project
by Andres Mejia 26 Aug '11

26 Aug '11

Hi, Keep up the great work. I was looking for an LGPL-2.1 crypto library that can be used as an alternative to libgcrypt. Reason being can best be explained at [1]. So here are some questions I have. GNU Nettle is going to stick with LGPL-2.1+ correct? I ask this since I'm currently working on implementing full RAR archive support with libarchive, to ultimately be used in XBMC Media Center. XBMC is GPL-2+ and we have no desire to go to GPL-3. Another question, the only thing I see missing in nettle that libarchive can make use of is RIPEMD-160. In case I want to submit patches, I should submit them here correct? Also, I suppose if I wanted to submit patches, there's no issue in porting code from gcrypt over to nettle correct? I think it would be easier (and faster) to reuse the implementation in gcrypt than to implement the algorithm from scratch. -- Regards, Andres Mejia 1. http://lists.debian.org/debian-devel/2011/04/msg01170.html

3 5

ECC support
by Nikos Mavrogiannopoulos 15 Aug '11

15 Aug '11

Hello, This patch adds ECC support using the GnuTLS libtomcrypt adaptation. regards, Nikos btw. I had issues building the cvs version. The compilation was failing: nettle-hash.o: In function `list_algorithms': /home/nmav/cvs/lsh/nettle/tools/nettle-hash.c:49: undefined reference to `nettle_hashes'

2 5

pkg-config
by nisse＠lysator.liu.se 20 Jul '11

20 Jul '11

I just checked in nettle.pc.in and hogweed.pc.in. configure then generates nettle.pc and hogweed.pc, for use wiith pkg-config. I don't have any previous experience with pkg-config, so comments are much appreciated. Not yet any make rules to install them. I don't know if installation should be unconditional, or if one should first check, somehow, if pkg-config is installed. (And then hogweed.pc should be installed only if the hogweed library is built and installed). Apparantly, at least one user wants pkg-config support, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634294 Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.

1 0

Jump to page:

2025

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