Tasks for 1.6
jussi.kivilinna at iki.fi
Tue Nov 26 13:31:39 CET 2013
On 07.11.2013 10:11, Werner Koch wrote:
> some notes on what I think should be done before a 1.6 release.
> - Decide what to do with MACing algorithms.
> - Check that the recent changes in gcry_pk_ don't break too much (this
> is mainly about GnuPG and something I will take care about).
> - Check that the new threading initialization scheme works on major
> - Look for rarely used function we may want to remove from the API (we
> have an ABI change anyway)
> - Fix side-channel weaknesses in the new ECC code.
> - Run test builds on all Debian supported platforms
I've only have access to x86 and ARM, but I've tested libgcrypt on other archs with help of cross-compilers and qemu userspace emulation.
List of tested builds:
- i386-linux-gnu (native)
- x86_64-linux-gnu (native)
- x86_64-linux-gnux32 (native)
- arm-linux-gnueabihf (native)
- mingw32 (wine)
- powerpc-linux-gnu (qemu)
- aarch64-linux-gnu (qemu)
- mips-linux-gnu (qemu)
- mipsel-linux-gnu (qemu)
- sparc-linux-gnu (qemu)
> After that I think the release of 1.6 is justified. Experience has
> shown that we will need to release a couple of fixes soon after 1.6.0.
> The important thing is that we keep the ABI stable after 1.6.0.
> I would like to do a release within the next 4 weeks.
More information about the Gcrypt-devel