nettle-bugs

nettle-bugs@lists.lysator.liu.se

2196 discussions

ANNOUNCE: nettle-1.7
by nisse＠lysator.liu.se 11 Mar '03

11 Mar '03

There have been lot of smaller and larger changes since the previous release half a year ago, so I've decided to package up the current code as a release. There's also one new section in the manual, describing DSA. NEWS for the 1.7 release Implemented DSA. Renamed RSA functions for consistency. Now it's rsa_public_key_init, not rsa_init_public_key, etc. Both RSA and DSA now have sign/verify functions that take the hash digest as argument. A rewritten and much more powerful sexp-conv program. Other changes to the sexp code, in particular updating it to the latest SPKI draft. Building nettle as a shared library (ELF only) seems to work. The version number is increased, so the library "soname" for this release is "libnettle.so.1". Bugfixes. Fixes for build and portability problems. Available at http://www.lysator.liu.se/~nisse/archive/nettle-1.7.tar.gz ftp://ftp.lysator.liu.se/pub/security/lsh/nettle-1.7.tar.gz Regards, /Niels

1 0

libspki (informal announce)
by nisse＠lysator.liu.se 11 Mar '03

11 Mar '03

This is the first informal announcement of libspki. SPKI, the Simple Public Key Infrastructure, is a sane way of using certificates. The original design is by Carl Ellison and Ron Rivest. The emphasis, at least from my point of view, is on association of authorization to keys (in contrast to X.509, which tries to bind X.500 names to keys), and on delegation of some or all of one's authorization. For some background, read RFC 2693. I think the primary applications where SPKI would be useful is in authentication (like public key ssh login, as well as host authentication), access control for various network servers, perhaps also peer-to-peer servers, etc. I've been working on an SPKI library from time to time since November last year. As the name promises, it *is* pretty simple. I have the most important features in place and it's still less than 7000 lines. For an example of what the objects look like, see the delegation testcase, <URL: http://cvs.lysator.liu.se/viewcvs/viewcvs.cgi/lsh/src/spki/testsuite/delega…> The purpose if this announcement is to find out if there are any other people in the community who are interested in SPKI. I'm not in a desperate need for coding help, but I could really use feedback on the code and functionality: If the interfaces are reasonable or need generalization, which of the missing features are important, how to organize the directory of SPKI-related information, which parts are in the most need of documentation, etc. To me, SPKI seems like the obvious way to go whenever one needs public keys, and has the luxury of not having to be backwards compatible with X.509. (Actually, SPKI is designed so that it *can* interoperate with alien PKI stuff, such as X.509, but I'm not going to write that code any time soon). There's no polished distribution, so the easiest way to try out libspki is to pull the latest lsh from cvs. For further pointers and instructions, see <URL: http://www.lysator.liu.se/~nisse/libspki>. Please let me know what you think about it. Happy hacking, /Niels

1 0

problems with --enable-shared
by James Ralston 30 Dec '02

30 Dec '02

I tried building nettle 1.6 with --enabled-shared on Red Hat Linux 8.0 on x86. The command to build the shared library doesn't get the soname or the filename correct: gcc -shared -Wl,-soname=libnettle.so. aes_p.o [...] nettle-openssl_p.o -o libnettle.so The attached patch fixes the problem. The example programs are built like this: [...] ../libnettle.a -lcrypto -lgmp In order to test the shared libraries, that needs to be something like this: [...] -L.. -lnettle -lcrypto -lgmp That will work even if a shared library wasn't build. The example programs will need to be invoked with LD_LIBRARY_PATH set appropriately. However, when I tested linking one of the example programs with the shared library, it failed: gcc -I.. -g -O2 -ggdb3 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -Wbad-function-cast -Wnested-externs -o rsa-keygen rsa-keygen.o io.o -L.. -lnettle -lcrypto -lgmp ../libnettle.so: undefined reference to `memxor' collect2: ld returned 1 exit status I haven't had time to look at this one any further... Regards, -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA

2 9

base64
by nisse＠lysator.liu.se 19 Oct '02

19 Oct '02

I've reorganized the base64 code again. The goal has been to support *both* simple "one-shot" encoding, and streamed operation. The declarations from the new base64.h are included below. For the actual code, see the cvs repository (http://cvs.lysator.liu.se/viewcvs/viewcvs.cgi/lsh/src/nettle/?cvsroot=lsh). Comments are welcome. /Niels #define BASE64_BINARY_BLOCK_SIZE 3 #define BASE64_TEXT_BLOCK_SIZE 4 /* Base64 encoding */ /* Maximum length of output for base64_encode_update. NOTE: Doesn't * include any padding that base64_encode_final may add. */ /* We have at most 4 buffered bits, and a total of (4 + length * 8) bits. */ #define BASE64_ENCODE_LENGTH(length) (((length) * 8 + 4)/6) /* Maximum lengbth of output generated by base64_encode_final. */ #define BASE64_ENCODE_FINAL_LENGTH 3 /* Exact length of output generated by base64_encode_raw, including * padding. */ #define BASE64_ENCODE_RAW_LENGTH(length) ((((length) + 2)/3)*4) struct base64_encode_ctx { unsigned word; /* Leftover bits */ unsigned bits; /* Number of bits, always 0, 2, or 4. */ }; void base64_encode_init(struct base64_encode_ctx *ctx); /* Encodes a single byte. Returns amoutn of output (always 1 or 2). */ unsigned base64_encode_single(struct base64_encode_ctx *ctx, uint8_t *dst, uint8_t src); /* Returns the number of output characters. DST should point to an * area of size at least BASE64_ENCODE_LENGTH(length). */ unsigned base64_encode_update(struct base64_encode_ctx *ctx, uint8_t *dst, unsigned length, const uint8_t *src); /* DST should point to an area of size at least * BASE64_ENCODE_FINAL_SIZE */ unsigned base64_encode_final(struct base64_encode_ctx *ctx, uint8_t *dst); /* Lower level functions */ /* Encodes a string in one go, including any padding at the end. * Generates exactly BASE64_ENCODE_RAW_LENGTH(length) bytes of output. * Supports overlapped operation, if src <= dst. */ void base64_encode_raw(uint8_t *dst, unsigned length, const uint8_t *src); void base64_encode_group(uint8_t *dst, uint32_t group); /* Base64 decoding */ /* Maximum length of output for base64_decode_update. */ /* We have at most 6 buffered bits, and a total of (length + 1) * 6 bits. */ #define BASE64_DECODE_LENGTH(length) ((((length) + 1) * 6) / 8) struct base64_decode_ctx { enum { BASE64_DECODE_OK, BASE64_DECODE_ERROR, BASE64_DECODE_END } status; unsigned word; /* Leftover bits */ unsigned bits; /* Number buffered bits */ }; void base64_decode_init(struct base64_decode_ctx *ctx); /* Returns the number of output characters. DST should point to an * area of size at least BASE64_DECODE_LENGTH(length). */ unsigned base64_decode_update(struct base64_decode_ctx *ctx, uint8_t *dst, unsigned length, const uint8_t *src); /* Returns 1 on success. */ int base64_decode_status(struct base64_decode_ctx *ctx); #endif /* NETTLE_BASE64_H_INCLUDED */

1 0

ANNOUNCE: Nettle-1.6
by nisse＠lysator.liu.se 03 Oct '02

03 Oct '02

NEWS for the 1.6 release Optimized assembler implementations of aes, for sparc and x86. The aes interface has changed slightly. The function aes_set_key is no more. Instead one has to use aes_set_encrypt_key or aes_set_decrypt_key. Sorry about that. New example programs, rsa-keygen, rsa-sign and rsa-verify, located in the examples directory. New configure option --enable-shared, which builds a shared library. Not tested. New experimental features, including sexp parsing and formatting, and changes to base64 encoding and decoding. The interfaces to these functions are subject to change, and are documented only in the source code. I'll appreciate comments on the new things, in particular the --enable-shared option, and the new sexp functions, which probably can be simplified a little. I've also created a nettle mailing list, see <URL: http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs> for subscription information. I expect it to be a low-volume list. Further announcements of nettle releases will be sent to that list, and probably not to the lsh or the gcrypt lists. nettle-1.6 is available at http://www.lysator.liu.se/~nisse/archive ftp://ftp.lysator.liu.se/pub/security/lsh Happy hacking, /Niels Möller

1 0

Ping
by nisse＠lysator.liu.se 02 Oct '02

02 Oct '02

Foo?

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