From a.radke at arcor.de Fri Aug 12 10:14:30 2011 From: a.radke at arcor.de (Andreas Radke) Date: Fri, 12 Aug 2011 10:14:30 +0200 Subject: libgcrypt 1.5.0 aes-ni test suite fails for i686 In-Reply-To: <20110708161552.7718d50b@workstation64.home> References: <20110708161552.7718d50b@workstation64.home> Message-ID: <20110812101430.1ebb40c5@workstation64.home> Am Fri, 8 Jul 2011 16:15:52 +0200 schrieb Andreas Radke : > I'm packaging libgcrypt for ArchLinux. My build system has a core i7 > AES capable cpu running x86_64 kernel and userland. The x86_64 package > builds fine in our chroot and passes all tests. > > Building in an i686 chroot gives segfaults in 3 tests. Is this an > expected behavior or a bug? Adding --disable-aesni-support makes it > pass all tests also for i686. > > -Andy > Anybody around who can help me to track this down and find a fix? We've just fixed a very similar segfault issue in gnutls 3.0.0 related to AES-NI and alignment issues. Please have a look at this commit: http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=commitdiff;h=d21285196611811120ff1ba41e64f716f244f3d8 I can try to give backtraces or whatever we need. -Andy From drizt at land.ru Fri Aug 26 18:53:40 2011 From: drizt at land.ru (Ivan Romanov) Date: Fri, 26 Aug 2011 22:53:40 +0600 Subject: Another misspeled in docs Message-ID: <4E57CF94.40808@land.ru> @deftypefun {const char *}*gcry_strsource* (@w{gcry_error_t @var{err}}) The function @code{*gcry_strerror*} returns a pointer to a statically allocated string containing a description of the error source contained in the error value @var{err}. This string can be used to output a diagnostic message to the user. @end deftypefun -------------- next part -------------- An HTML attachment was scrubbed... URL: From drizt at land.ru Fri Aug 26 17:40:34 2011 From: drizt at land.ru (Ivan Romanov) Date: Fri, 26 Aug 2011 21:40:34 +0600 Subject: Misspeled in docs Message-ID: <4E57BE72.60108@land.ru> Hello. Have a look at gcrypt.texi @noindent The result is 0 for success (i.e. the data matches the signature), or an error code where the most relevant code is @code*{GCRYERR_BAD_SIGNATURE}* to indicate that the signature does not match the provided data. Maybe must be*GPG_ERR_BAD_SIGNATURE* -------------- next part -------------- An HTML attachment was scrubbed... URL: From linux at horizon.com Mon Aug 29 16:12:30 2011 From: linux at horizon.com (George Spelvin) Date: 29 Aug 2011 10:12:30 -0400 Subject: IDEA support Message-ID: <20110829141230.8157.qmail@science.horizon.com> > Maybe after the US patent expires next year. Er... the U.S. patent expired May 16. It claims a priority date of the international patent application on 16 May 1991, so expired 20 years after that. The Ascom Tech lawyers maximized the patent duration carefully. The Swiss patent was applied for on 18 May 1990, and one has 1 year to apply in other jurisdictions. They used the Patent Cooperation Treaty process to apply simultaneously in other countries at the last possible moment. Even though the U.S.-specific part was started later, the effective date of the application, when the 20-year clock began, was the PCT application. It can't be later, becuase if it were, the Swiss patent would constitute prior disclosure.