Re: Compile issue on Solaris 11.3

On Sun, Mar 28, 2021 at 4:18 AM Niels Möller wrote: > > Jeffrey Walton writes: > > >> I added --disable-x86-sha-ni and it still produces the error. How is > >> the ASM being used if it is disabled??? > > You need to choose *either* --enable-fat (now the default

Re: Compile issue on Solaris 11.3

On Sat, Mar 27, 2021 at 9:34 PM Jeffrey Walton wrote: > This makes no sense... > > I added --disable-x86-sha-ni and it still produces the error. How is > the ASM being used if it is disabled??? Here's a demonstration of the configuration problem. #!/usr/bin/env bash NETTLE=nettle-3

Re: Compile issue on Solaris 11.3

On Mon, Jan 4, 2021 at 4:00 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > Hi Everyone, > > > > I bumped to Nettle 3.7. The build is resulting in: > > Clearly, the assembler doesn't know of the sha-related instructions > (introduced in 2013, accordin

[no subject]

Hi Everyone, Here's the result of building Nettle 3.7.2 on Solaris 11.3, i86pc: /bin/gcc -I. -I/opt/ssh/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 -m64 -march=native -fPIC -pthread -ggdb3 -Wall -W -Wno-sign-compare -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith

Re: xts.c:59: warning: integer constant is too large for ‘long’ type

On Thu, Mar 25, 2021 at 2:45 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > This is building Nettle 3.7.2 on a PowerMac with OS X 10.5: > > > > /usr/bin/cc -I. -I/usr/local/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 > > -mlong-double-64 -fno-common -maltiv

Re: libhgwwed has gone missing...

On Thu, Mar 25, 2021 at 1:20 PM Jeffrey Walton wrote: > > On Thu, Mar 25, 2021 at 3:48 AM Niels Möller wrote: > > > > Jeffrey Walton writes: > > > > > It looks like Nettle is no longer building or installing hogweed on > > > some Apple platforms. >

xts.c:59: warning: integer constant is too large for ‘long’ type

This is building Nettle 3.7.2 on a PowerMac with OS X 10.5: /usr/bin/cc -I. -I/usr/local/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 -mlong-double-64 -fno-common -maltivec -fPIC -pthread -ggdb3 -Wno-pointer-sign -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes

Re: libhgwwed has gone missing...

On Thu, Mar 25, 2021 at 3:48 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > It looks like Nettle is no longer building or installing hogweed on > > some Apple platforms. > > > > This is from a PowerMac G5 running OS X 10.5: > > Most likely the c

Re: libhgwwed has gone missing...

The last version of Nettle to build and install Hogweed on PowerMac was 3.5. I think this flew under the radar because prefix=/usr/local. Through subsequent upgrades, GnuTLS was picking up the old version of Hogwwed. Jeff On Wed, Mar 24, 2021 at 9:47 PM Jeffrey Walton wrote: > > It look

libhgwwed has gone missing...

It looks like Nettle is no longer building or installing hogweed on some Apple platforms. This is from a PowerMac G5 running OS X 10.5: $ ls /usr/local/lib | grep -E 'gmp|nettle|hogweed' libgmp.10.dylib libgmp.a libgmp.dylib libgmp.la libnettle.8.2.dylib libnettle.8.3.dylib libnettle.8.dylib

Nettle 3.7.2 and OS X 10.5

Hi Everyone, I'm testing Nettle 3.7.2 on a PowerMac with OS X 10.5 . I added -maltivec to CFLAGS and CXXFLAGS. I enabled Altivec builds with --enable-power-altivec and --enable-fat. Auditing the dylib it appears Altivec was not engaged: $ otool -tV /usr/local/lib/libnettle.dylib | grep perm

Nettle 3.7.2 and OS X 10.12.6

And it looks like examples are not quite working either: $ make check ... All 110 tests passed Making check in examples TEST_SHLIB_DIR="/Users/jwalton/Build-Scripts/nettle-3.7.2/.lib" \ srcdir="." EMULATOR="" EXEEXT="" \ ".."/run-tests

Re: Nettle 3.7.2 and OS X 10.12.6

On Sun, Mar 21, 2021 at 6:18 PM Jeffrey Walton wrote: > > $ make check > ... > ../run-tests aes-test arcfour-test arctwo-test blowfish-test > bcrypt-test cast128-test base16-test base64-test camellia-test > chacha-test cnd-memcpy-test des-test des3-test md2-test md4-t

Nettle 3.7.2 and OS X 10.12.6

$ make check ... ../run-tests aes-test arcfour-test arctwo-test blowfish-test bcrypt-test cast128-test base16-test base64-test camellia-test chacha-test cnd-memcpy-test des-test des3-test md2-test md4-test md5-test md5-compat-test memeql-test memxor-test gosthash94-test ripemd160-test

Re: Add AES Key Wrap (RFC 3394) in Nettle

On Tue, Feb 2, 2021 at 5:44 PM Nicolas Mora wrote: > > Hello, > > I've added a merge request to implement AES key wrap and unwrap in > Nettle [1]. > > The MR is not complete, because the tests haven't been pushed yet and > the documentation is missing, but if the new functionality is welcome to >

Re: Arcfour status

On Sun, Feb 14, 2021 at 5:36 AM Niels Möller wrote: > > I've had a report (from Matthew Kempe) about another problem with the > openssl benchmarking code. It fails on FreeBSD, because there (and > possible in other environments too) openssl has been configured without > RC4 (aka arcfour) support.

Re: GnuTLS testsuite error on ppc64 after nettle upgrade

On Tue, Feb 9, 2021 at 3:07 PM Niels Möller wrote: > > ni...@lysator.liu.se (Niels Möller) writes: > > > I would guess that means that we got 209 bytes, including the 16-byte > > poly1305 authentication tag. Message size is then 209 - 16 = 193 bytes. > > If the first byte is a TLS packet type,

Re: [S390x] Optimize AES modes

On Wed, Feb 3, 2021 at 11:13 AM Niels Möller wrote: > ... > I've had look at the terms and conditions, > http://security.marist.edu/LinuxOne/TC.PDF. Most of it looks very > reasonable, but there are a few items that I find a bit unclear: > > 9. [...] You agree to obey all relevant New York State

Re: [AArch64] Optimize GHASH

On Tue, Feb 2, 2021 at 8:19 AM Jeffrey Walton wrote: > > On Tue, Feb 2, 2021 at 8:00 AM Michael Weiser wrote: > > > > > > llvm-as wouldn't recognize pmull instruction without > > > > adding -march=armv8-a+crypto flag at least with the version I use > &

Re: [AArch64] Optimize GHASH

On Tue, Feb 2, 2021 at 8:00 AM Michael Weiser wrote: > > > > llvm-as wouldn't recognize pmull instruction without > > > adding -march=armv8-a+crypto flag at least with the version I use "3.8.1" > > 3.8.1 was released in 2017. It might not support recent > aarch64 additions regarding .arch

Re: [AArch64] Optimize GHASH

On Fri, Jan 22, 2021 at 5:48 PM Maamoun TK wrote: > > On Fri, Jan 22, 2021 at 1:45 AM Michael Weiser > wrote: > > > Do you think it makes sense to try and adjust the code to work with the > > BE layout natively and have a full 128bit reverse after ldr-like loads > > on LE instead (considering

Re: [AArch64] Optimize GHASH

On Tue, Jan 5, 2021 at 8:23 AM Niels Möller wrote: > > ni...@lysator.liu.se (Niels Möller) writes: > > > ... > The reference manual says > > Armv8 can support the following levels of support for Advanced SIMD and > floating-point instructions: > > *Full SIMD and floating-point support without

Compile issue on Solaris 11.3

Hi Everyone, I bumped to Nettle 3.7. The build is resulting in: gcc -I. -I/export/home/jwalton/tmp/ok2delete/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 -m64 -march=native -fPIC -pthread -ggdb3 -Wall -W -Wno-sign-compare -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes

Re: Release of Nettle-3.7?

On Tue, Dec 29, 2020 at 5:15 PM Michael Weiser wrote: > > ... > Do you (or anybody else) have a hardware arm board for testing, possibly > with a Cortex A8 or A9 implementation to see how it behaves there? I've got a Wnadboard/Cortex-A9 and Tinkerboard/Cortex-A17 hanging off the internet with

Re: Failing gnutls tests

On Mon, Dec 28, 2020 at 7:59 AM Andreas Metzler wrote: > > On 2020-12-28 Niels Möller > wrote: > > Hi, recent gnutls tests on the gitlab ci system all fail the test > > "testpkcs11.sh". See e.g., > > https://gitlab.com/gnutls/nettle/-/jobs/932664781. First failure was an > > a merge commit with

Re: Release of Nettle-3.7?

On Sat, Dec 19, 2020 at 4:44 AM Niels Möller wrote: > > Amos Jeffries writes: > > > I would have though this needs a soname bump. Otherwise software built > > to use bcrypt might try to link to the old version with same soname. > > My understanding is that one usually doesn't bump the soname

Re: [AArch64] Optimize GHASH

On Fri, Dec 18, 2020 at 11:31 AM Niels Möller wrote: > > Maamoun TK writes: > > > It seems gcc for aarch64 doesn't support building 32-bit binaries, maybe we > > should remove the check of ABI since 64-bit is the only option. > > Ok, that's a bit confusing. There's a command line flag for it,

Re: CPU feature detection for Nettle-3.7?

On Sat, Dec 19, 2020 at 3:58 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > It would be nice if cpu feature detection for fat builds made it into > > the next release. It is easier than arm64, and it is needed to avoid > > crashes at runtime. > >

CPU feature detection for Nettle-3.7?

On Tue, Dec 15, 2020 at 10:47 AM Niels Möller wrote: > > Hi, I wonder if it would make sense to try to cut a release pretty soon > (and without any arm64 changes)? Previous release was made end of April, > and there's been quite a few improvements since then. It would be nice if cpu feature

Re: PPC chacha

On Wed, Nov 25, 2020 at 3:22 AM Niels Möller wrote: > > Maamoun TK writes: > > > On POWER9 I got the following benchmark result: > > > > ./configured: > > chacha encrypt 308.58 > > chacha decrypt 325.87 > > ./configured --enable-power-altivec "master branch": > > chacha encrypt

Re: [PowerPC] GCM optimization

On Fri, Nov 20, 2020 at 3:39 PM Maamoun TK wrote: > > -- Forwarded message - > From: Maamoun TK > Date: Thu, Nov 12, 2020 at 7:42 PM > Subject: Re: [PowerPC] GCM optimization > To: Niels Möller > > On Thu, Nov 12, 2020 at 6:40 PM Niels Möller wrote: > > > I gave it a test run

Re: PPC chacha

On Sat, Nov 21, 2020 at 11:23 AM David Edelsohn wrote: > > On Sat, Nov 21, 2020 at 10:57 AM Jeffrey Walton wrote: > > > > On Sat, Nov 21, 2020 at 10:20 AM David Edelsohn wrote: > > > > > > Please don't target Power7. Please target Power9, or at least Power

Re: PPC chacha

On Sat, Nov 21, 2020 at 10:20 AM David Edelsohn wrote: > > Please don't target Power7. Please target Power9, or at least Power8. > > The PPC64LE Linux ABI specifies Power8 as the minimum ISA. > > Power ISA 2.07 is Power8. ISA 3.0 is Power9. ISA 3.1 is Power10. Small nit... PowerMac G4's and

Re: PPC chacha

On Fri, Nov 20, 2020 at 3:40 PM Niels Möller wrote: > > ni...@lysator.liu.se (Niels Möller) writes: > > > It could likely be speedup further by processing 2, 3 or 4 blocks in > > parallel. > > I've given 2 blocks in parallel a try, but not quite working yet. My > work-in-progress code below. > >

Re: GCM with ARM Neon

On Sun, Oct 11, 2020 at 2:03 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > I may be mistaken, but I believe 64-bit poly multiplies are available. > > Or they are available on Aarch64 with Crypto extensions. > > I'm looking in the Arm Instruction Set Refer

Re: GCM with ARM Neon (was: Re: [PATCH] "PowerPC64" GCM support)

On Sun, Oct 11, 2020 at 1:42 PM Niels Möller wrote: > > ni...@lysator.liu.se (Niels Möller) writes: > > > So if we have the input in register A (loaded from memory with no > > processing besides ensuring proper *byte* order), and precompute two > > values, M representing b_1(x) x^64 + c_1(x), and

Re: [PATCH] "PowerPC64" GCM support

On Sat, Oct 3, 2020 at 7:00 PM Maamoun TK wrote: > ... > 2. ... has different name > on CLANG '__builtin_altivec_crypto_vpmsumd' so we will end up using a lot > of conditions to check the variant of compiler plus writing inline assembly > code for 'vpmsumd' in case the variant has intrinsic issue

Re: PPC chacha

On Fri, Sep 25, 2020 at 11:04 AM Jeffrey Walton wrote: > > On Fri, Sep 25, 2020 at 10:25 AM Niels Möller wrote: > > > > Jeffrey Walton writes: > > ... > It should be easy enough to test. Start with a counter of 0xfff8 > and encrypt a couple of [64-byte] b

Re: PPC chacha

On Fri, Sep 25, 2020 at 10:25 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > I believe the 64-bit adds (addudm) and subtracts (subudm) require > > POWER8. > > I don't think there are any 64-bit adds in my chacha code, only 32-bit, > vadduwm. The chacha st

Re: PPC chacha

On Fri, Sep 25, 2020 at 7:43 AM Maamoun TK wrote: > ... > > I'm not sure where it fits under powerpc64. The code doesn't need any > > cryptographic extensions, but it depends on vector instructions as well > > as VSX registers (for the unaligned load and store instructions). So I'd > > need

Re: PPC chacha

On Thu, Sep 24, 2020 at 3:46 PM Niels Möller wrote: > > I'm trying to learn a bit of ppc assembly. Below is an implementation of > _chacha_core. Seems to work, when tested on gcc112.fsffrance.org (just > put the file in the powerpc64 directory and reconfigure). This machine > is little-endian, I

Re: [PATCH 4/6] "PowerPC64" Add fat build

On Wed, Aug 19, 2020 at 5:42 PM Maamoun TK wrote: > ... > > Another question: When looking at the powerpc64 things in configure.ac, > > I wonder if powerpc64 supports 32-bit binaries, which would be built > > with something like CC='gcc -m32' ? > > > > If 32-bit builds are possible, and are

Re: [Patch] "PowerPC64" Add README (Reformatted)

On Sun, Aug 2, 2020 at 2:12 PM Niels Möller wrote: > > Maamoun TK writes: > > > --- > > powerpc64/README | 73 > > > > 1 file changed, 73 insertions(+) > > create mode 100644 powerpc64/README > > Merged to the power-asm-wip branch (there

Re: [PowerPC64] Add AIX to cpu detection

On Mon, Jul 20, 2020 at 12:18 PM Maamoun TK wrote: > > --- > fat-ppc.c | 29 - > 1 file changed, 20 insertions(+), 9 deletions(-) > > diff --git a/fat-ppc.c b/fat-ppc.c > index e09b2097..eca689fe 100644 > --- a/fat-ppc.c > +++ b/fat-ppc.c > @@ -39,10 +39,17 @@ >

Re: Handling of ORIGIN-based rpaths and runpaths

On Mon, Jul 20, 2020 at 8:04 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > You have to fix the makefiles. If you escape the dollar signs in > > LDFLAGS, then Autotools will fail its conftests because they don't use > > a makefile. Autotools conftests use C

Re: Handling of ORIGIN-based rpaths and runpaths

On Fri, Jul 17, 2020 at 3:24 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > Hi Everyone, > > > > I build OpenSSH for downlevel machines, like OS X and Solaris. I > > install into /opt/ssh, and I use a runpath of $ORIGIN/../lib. The > > LDFLAGS

Re: Assembly recipe missing ASFLAGS

aes-decrypt-internal.s should be built using ASFLAGS, too. The recipe should look something like: %.s: $(CC) $(CPPFLAGS) $(CFLAGS) $(ASFLAGS) -c $< -o $@ Otherwise, the object file has an executable stack. Jeff On Fri, Jul 17, 2020 at 4:05 PM Jeffrey Walton wrote: > > Hi Everyone, &

Assembly recipe missing ASFLAGS

Hi Everyone, I noticed *.s recipes do not use ASFLAGS. ASFLAGS includes -Wa,--noexecstack: ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs

relocation error: R_AMD64_64

Hi Everyone, I'm seeing a fair amount of "ld: warning: relocation error: R_AMD64_64" when linking from nettle-3.6 release tarball: gcc -g2 -O2 -m64 -march=native -fPIC -pthread -ggdb3 -Wall -W -Wno-sign-compare -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith

Handling of ORIGIN-based rpaths and runpaths

Hi Everyone, I build OpenSSH for downlevel machines, like OS X and Solaris. I install into /opt/ssh, and I use a runpath of $ORIGIN/../lib. The LDFLAGS are: -Wl,-runpath,'$ORIGIN/../lib' -Wl,-runpath,$(prefix)/lib -Wl,--enable-new-dtags I noticed Nettle does not handle the ORIGIN-based

Re: [Patch] Optimize AES and GHASH for PowerPC64 (support little-endian and big-endian)

on POWER8: https://github.com/dot-asm/cryptogams/blob/master/ppc/aesp8-ppc.pl. Andy uses it for the user's key and data. Jeff > On Tue, Jun 30, 2020 at 12:35 PM Jeffrey Walton wrote: > > > On Tue, Jun 30, 2020 at 5:29 AM Jeffrey Walton wrote: > > > > > > On

Re: [Patch] Optimize AES and GHASH for PowerPC64 (support little-endian and big-endian)

On Tue, Jun 30, 2020 at 5:29 AM Jeffrey Walton wrote: > > On Tue, Jun 30, 2020 at 5:14 AM Maamoun TK wrote: > > > > Patch implementation benchmark for GCM_AES (Tested on POWER8): > > little-endian: > > - Encrypt x~17.5 of nettle C implementation > > - Decry

Re: [Patch] Optimize AES and GHASH for PowerPC64 (support little-endian and big-endian)

On Tue, Jun 30, 2020 at 5:14 AM Maamoun TK wrote: > > Patch implementation benchmark for GCM_AES (Tested on POWER8): > little-endian: > - Encrypt x~17.5 of nettle C implementation > - Decrypt x~17.5 of nettle C implementation > - Update x~30 of nettle C implementation > big-endian: > - Encrypt

Re: Nettle backup maintainers?

On Thu, Apr 16, 2020 at 12:50 PM Aapo Talvensaari wrote: > > On Thu, Apr 16, 2020 at 12:44 AM Jeffrey Walton wrote: >> ... > I agree with Tim. If project is of any importance, as I think Nettle is, > there is no > problem in finding a new maintainer in case it is n

Re: Nettle backup maintainers?

On Thu, Apr 16, 2020 at 3:34 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > Does Nettle have backup maintainers? If so, can you name them and > > provide their public keys in case something happens to Niels. > > I don't think the current situation warra

Nettle backup maintainers?

Hi Everyone/Niels, Forgive me for asking... Does Nettle have backup maintainers? If so, can you name them and provide their public keys in case something happens to Niels. Sweden has been criticized for its handling of the coronavirus. The country seems to be engaging in relatively risky

Re: Nettle-3.6 soon

On Mon, Apr 13, 2020 at 12:54 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > On Mon, Apr 13, 2020 at 10:09 AM Niels Möller wrote: > >> > >> As far as I'm aware, that should fix BSDs and other systems disliking > >> relative names in LD_LIRBA

Re: Nettle-3.6 soon

On Mon, Apr 13, 2020 at 10:09 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > The failure will also affect some of the BSDs. I know it affects NetBSD, > > too. > > I made a commit a while ago to always use an absolute name (based on > autoconf's

Re: Nettle-3.6 soon

On Mon, Apr 13, 2020 at 8:16 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > nettle-3.6rc1.tar.gz tested OK on an old PowerMac with OS X 10.5 and > > an Intel Mac Mini with OS X 10.12.6 with SIP. > > Thanks for testing. Regarding the remaining DYLD_LIBRAR

Re: Nettle-3.6 soon

On Mon, Apr 13, 2020 at 7:10 AM Jeffrey Walton wrote: > > On Sun, Apr 5, 2020 at 2:03 PM Niels Möller wrote: > > > > I've updated the NEWS file, and I don't think there are any easy changes > > pending. Please let me know ASAP if there's anything missing in NEWS, or >

Re: Nettle-3.6 soon

On Sun, Apr 5, 2020 at 2:03 PM Niels Möller wrote: > > I've updated the NEWS file, and I don't think there are any easy changes > pending. Please let me know ASAP if there's anything missing in NEWS, or > if there are additional changes you think ought to be included before > release. > > I

Re: Failure of gnutls ci build

On Tue, Mar 31, 2020 at 7:42 AM Jeffrey Walton wrote: > > On Mon, Mar 30, 2020 at 7:23 AM Niels Möller wrote: > > > > I committed a change to update nettle version numbers, which implies a > > new symbol version for internal symbols. > > > > That seems to

Re: Nettle 3.5.1 and OS X 10.12 patch

On Wed, Apr 1, 2020 at 2:06 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > Tested mostly OK on my mac-mini: > > Thanks for testing. > > > dyld: Library not loaded: /Users/jwalton/tmp/nettle/lib/libnettle.7.dylib > > Is this the expected location aft

Re: Nettle 3.5.1 and OS X 10.12 patch

On Tue, Mar 31, 2020 at 2:08 PM Niels Möller wrote: > > ni...@lysator.liu.se (Niels Möller) writes: > > > I think a reasonable way is to add > > > > abs_top_builddir = @abs_top_builddir@ > > > > TEST_SHLIB_DIR = "${abs_top_builddir}/.lib" > > > > to config.make.in, and use that to set

Re: Failure of gnutls ci build

On Mon, Mar 30, 2020 at 7:23 AM Niels Möller wrote: > > I committed a change to update nettle version numbers, which implies a > new symbol version for internal symbols. > > That seems to break the gnutls ci build, > https://gitlab.com/gnutls/nettle/-/jobs/487360242 > > The error is > > 1217

Re: Nettle 3.5.1 and OS X 10.12 patch

On Tue, Mar 31, 2020 at 6:44 AM Jeffrey Walton wrote: > > On Tue, Mar 31, 2020 at 6:30 AM Michael Weiser wrote: > > > > On Tue, Mar 31, 2020 at 05:51:38AM -0400, Jeffrey Walton wrote: > > > > > > > > In a quick test on Mojave it appears that any

Re: Nettle 3.5.1 and OS X 10.12 patch

On Tue, Mar 31, 2020 at 6:30 AM Michael Weiser wrote: > > On Tue, Mar 31, 2020 at 05:51:38AM -0400, Jeffrey Walton wrote: > > > > > > In a quick test on Mojave it appears that any attempt to setenv() a > > > > > variable that starts with DYLD_ is silently

Re: Nettle 3.5.1 and OS X 10.12 patch

On Tue, Mar 31, 2020 at 5:45 AM Michael Weiser wrote: > > On Tue, Mar 31, 2020 at 09:27:02AM +0200, Niels Möller wrote: > > > > In a quick test on Mojave it appears that any attempt to setenv() a > > > variable that starts with DYLD_ is silently ignored. Can you confirm > > > that? My testcase

Nettle 3.5.1 and OS X 10.12 patch

Hi Everyone/Niels, I've got a bare-bones Mac-mini without Xcode. It has CC Tools but that is it. It is in a stock configuration. When I attempt to run 'make check' nearly every test failed due to missing libnettle and libhogweed. The libraries were present in .lib/, but something was blowing

Re: [PATCH] x86: Build with -z ibt -z shstk if possible

On Mon, Mar 16, 2020 at 3:12 PM Jeffrey Walton wrote: > > On Mon, Mar 16, 2020 at 2:50 PM Niels Möller wrote: > > > > ... > > 2. What I tried to ask about in the message you reply to, was how to > >write a test within the Nettle testsuite, to verify that enablin

Re: [PATCH] x86: Build with -z ibt -z shstk if possible

On Mon, Mar 16, 2020 at 2:50 PM Niels Möller wrote: > > ... > 2. What I tried to ask about in the message you reply to, was how to >write a test within the Nettle testsuite, to verify that enabling CET >really has effect on a test executable (on systems where it is >expected to have

Re: [PATCH] x86: Add X86_ENDBR and CET marker to config.m4.in

On Sat, Mar 7, 2020 at 12:29 PM Jeffrey Walton wrote: > > On Sat, Mar 7, 2020 at 11:49 AM Niels Möller wrote: > > > > "H.J. Lu" writes: > > > > > Intel Control-flow Enforcement Technology (CET): > > > > > > https://software.intel.c

Re: [PATCH] x86: Add X86_ENDBR and CET marker to config.m4.in

On Sat, Mar 7, 2020 at 11:49 AM Niels Möller wrote: > > "H.J. Lu" writes: > > > Intel Control-flow Enforcement Technology (CET): > > > > https://software.intel.com/en-us/articles/intel-sdm > > > > contains shadow stack (SHSTK) and indirect branch tracking (IBT). When > > CET is enabled, ELF

Re: Please use -shared on Solaris. Don't use -G on Solaris

On Mon, Feb 3, 2020 at 12:26 AM Niels Möller wrote: > > Jeffrey Walton writes: > > > On Sun, Feb 2, 2020 at 11:48 PM Niels Möller wrote: > >> > >> I don't have any time to spend on testing with these systems or > >> compilers. Do you think i

Re: Please use -shared on Solaris. Don't use -G on Solaris

On Sun, Feb 2, 2020 at 11:06 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > When linking the shared object with -G on Solaris: > > > > gcc -g2 -O2 -m64 -march=native -fPIC -pthread -Wno-pointer-sign -Wall > > -W -Wmissing-prototypes -Wmissing

Re: Crash on Core-i7 8700 machine with --enable-x86-aesni and --enable-x86-sha-ni

On Sat, Feb 1, 2020 at 8:38 PM Jeffrey Walton wrote: > ... > I'm catching a crash with Nettle 3.5.1 on a Core-i7 8700 configured > with --enable-x86-aesni and --enable-x86-sha-ni. I verified the > compiler supports both AESNI and SHA. > ... > > Here is the logi

Crash on Core-i7 8700 machine with --enable-x86-aesni and --enable-x86-sha-ni

Hi Everyone, I'm catching a crash with Nettle 3.5.1 on a Core-i7 8700 configured with --enable-x86-aesni and --enable-x86-sha-ni. I verified the compiler supports both AESNI and SHA. Illegal instruction (core dumped) FAIL: hkdf PASS: salsa20 Illegal instruction (core dumped)

Please use -shared on Solaris. Don't use -G on Solaris

When linking the shared object with -G on Solaris: gcc -g2 -O2 -m64 -march=native -fPIC -pthread -Wno-pointer-sign -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -Wbad-function-cast -Wnested-externs -L/usr/local/lib -m64 -Wl,-R,'$ORIGIN/../lib'

sha1-compress-2.s:74: Error: no such instruction: `sha1rnds4 $0, %xmm5, %xmm4'

Hi Everyone, I'm working on Solaris 11.3 i86pc. I'm building the Nettle 3.5.1 release tarball. configure: summary of build options: Version: nettle 3.5.1 Host type: x86_64-sun-solaris2 ABI: 64 Assembly files:x86_64/fat x86_64 Install prefix:

Re: post-quantum crypto algorithms implementation

On Wed, Dec 11, 2019 at 2:46 AM Niels Möller wrote: > > johnjmar writes: > > > Are there any plans for post-quantum algorithms implementation in the > > library? > > No concrete plans, I'm afraid. Nettle is not close to the research > frontier; a new algorithm is usually added when there's some

Re: patch: fix check for __builtin_bswap64

On Thu, Dec 5, 2019 at 3:08 AM Niels Möller wrote: > ... > > Does OpenBSBs runtime linker look in /usr/local/lib by default? The > configure script also supports --with-lib-path=/usr/local/lib, which > will add a -L flag and in addition attempt to guess the proper > -R/-Wl,-rpath flags. The

Re: PowerMac G5 results

On Tue, Oct 29, 2019 at 3:01 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > Hi Everyone, > > > > I'm building Nettle 3.5.1 on an old PowerMac G5. > > > > gcc -I. -I/usr/local/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 -fPIC > > -pthread

PowerMac G5 results

Hi Everyone, I'm building Nettle 3.5.1 on an old PowerMac G5. gcc -I. -I/usr/local/include -DNDEBUG -DHAVE_CONFIG_H -g2 -O2 -fPIC -pthread -ggdb3 -Wno-pointer-sign -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -Wbad-function-cast -Wnested-externs

Re: [PATCH 2/3] build: add --disable-libdir-abi-detection

On Wed, Jun 26, 2019 at 12:43 PM Niels Möller wrote: > > Jeffrey Walton writes: > > >> From which autoconf version? I'd be happy to require a recent autoconf > >> and drop this code if it's no longer needed. When this hack was added, > >> it was the case tha

Re: [PATCH 1/3] build: allow overriding the debug flags

On Wed, Jun 26, 2019 at 9:22 AM Niels Möller wrote: > > Alon Bar-Lev writes: > > > I do not understand... In practice a package should not add by itself > > optimization or debug flags without consent (some --enable- argument), > > the fact that nettle is doing that is unexpected... > > I'm open

Re: Nettle-3.4.1rc1, addressing PKCS#1 side-channel leaks

On Sat, Jan 12, 2019 at 6:01 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > I recommend making folks explicitly ask for a debug build with > > -DNETTLE_DEBUG or similar. > > "Debug build" vs "release build" is a bit alien to the way

Re: Nettle-3.4.1rc1, addressing PKCS#1 side-channel leaks

On Sat, Jan 12, 2019 at 11:47 AM Niels Möller wrote: > > Nikos Mavrogiannopoulos writes: > ... > I'm also considering adding a few more configurations to the ci, > including "CC=gcc -std=c89", CPPFLAGS=-DNODEBUG and --disable-assembler. > Anything I have to keep in mind (e.g., limits on builder

Re: sec_powm.c:293: GNU MP assertion failed: enb >= windowsize

On Sat, Dec 29, 2018 at 9:07 PM Jeffrey Walton wrote: > > On Sat, Dec 29, 2018 at 2:17 PM Jeffrey Walton wrote: > > > > I'm trying to build Nettle 3.4.1 on Fedora 29, x64 (fully patched). > > Self tests are failing at: > > > > PASS: rsa-sec-decrypt >

Re: sec_powm.c:293: GNU MP assertion failed: enb >= windowsize

On Sun, Dec 30, 2018 at 5:27 PM Niels Möller wrote: > > It might also be a bug in the book-keeping of scratch space, leading to > some memory overwrite. Try running the test program under valgrind > and/or asan? Hey Niels, What is the test name and how do I run it? Given I've built the library

Re: sec_powm.c:293: GNU MP assertion failed: enb >= windowsize

On Sun, Dec 30, 2018 at 5:27 PM Niels Möller wrote: > > Jeffrey Walton writes: > > > I'm trying to build Nettle 3.4.1 on Fedora 29, x64 (fully patched). > > Self tests are failing at: > > > > PASS: rsa-sec-decrypt > > sec_powm.c:293: GNU

Re: sec_powm.c:293: GNU MP assertion failed: enb >= windowsize

On Sat, Dec 29, 2018 at 2:17 PM Jeffrey Walton wrote: > > I'm trying to build Nettle 3.4.1 on Fedora 29, x64 (fully patched). > Self tests are failing at: > > PASS: rsa-sec-decrypt > sec_powm.c:293: GNU MP assertion failed: enb >= windowsize > ../run-tests

error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode

Building on my HiKey, which is Aarch64. == $ gcc --version gcc (Debian/Linaro 4.9.2-10+deb8u1) 4.9.2 Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

sec_powm.c:293: GNU MP assertion failed: enb >= windowsize

Hi Everyone, I'm trying to build Nettle 3.4.1 on Fedora 29, x64 (fully patched). Self tests are failing at: PASS: rsa-sec-decrypt sec_powm.c:293: GNU MP assertion failed: enb >= windowsize ../run-tests: line 57: 22997 Aborted (core dumped) "$1" $testflags FAIL: rsa-compute-root

Re: x86 sha_ni

On Mon, Mar 12, 2018 at 4:23 PM, Amos Jeffries <squ...@treenet.co.nz> wrote: > On 13/03/18 08:44, Jeffrey Walton wrote: >> Check /proc/cpuinfo for the sha_ni flag. If present, then you can test >> the SHA extensions. >> >> SHA extensions made their debut in

Re: x86 sha_ni

On Mon, Mar 12, 2018 at 2:40 PM, Niels Möller wrote: > ni...@lysator.liu.se (Niels Möller) writes: > ... > > Now wired up for fat builds, changes pushed to the same branch. Looks good on a Celeron J3455 (https://www.amazon.com/dp/B01LYCDG4H): Without --enable-fat

Re: Deleting old AES api

On Mon, Mar 12, 2018 at 2:56 PM, Jeffrey Walton <noloa...@gmail.com> wrote: > On Mon, Mar 12, 2018 at 2:49 PM, Niels Möller <ni...@lysator.liu.se> wrote: >> Nikos Mavrogiannopoulos <n...@redhat.com> writes: >> >>> #ifdef __GNUC__ >>> # define _GN

Re: Deleting old AES api

On Mon, Mar 12, 2018 at 2:49 PM, Niels Möller wrote: > Nikos Mavrogiannopoulos writes: > >> #ifdef __GNUC__ >> # define _GNUTLS_GCC_VERSION (__GNUC__ * 1 + __GNUC_MINOR__ * 100 + >> __GNUC_PATCHLEVEL__) >> >> # if _GNUTLS_GCC_VERSION >= 30100 >> #

Re: [PATCH 1/2] Provide wrappers around OpenSSL AES GCM

On Sat, Feb 17, 2018 at 7:36 AM, Niels Möller <ni...@lysator.liu.se> wrote: > Jeffrey Walton <noloa...@gmail.com> writes: > >> But production is a different story The time for debugging is over... > > I would generally assume that there are a few bugs left in als

Re: [PATCH 1/2] Provide wrappers around OpenSSL AES GCM

On Sat, Feb 17, 2018 at 6:30 AM, Amos Jeffries <squ...@treenet.co.nz> wrote: > On 17/02/18 22:59, Jeffrey Walton wrote: >> On Sat, Feb 17, 2018 at 4:35 AM, Niels Möller wrote: >>> ... >>>> ... >>> It's not right to use assert on expressions w

Re: [PATCH 1/2] Provide wrappers around OpenSSL AES GCM

On Sat, Feb 17, 2018 at 4:35 AM, Niels Möller wrote: > ... >> @@ -80,7 +80,7 @@ openssl_evp_set_encrypt_key(void *p, const uint8_t *key, >> { >>struct openssl_cipher_ctx *ctx = p; >>ctx->evp = EVP_CIPHER_CTX_new(); >> - assert(EVP_EncryptInit_ex(ctx->evp, cipher,

  1   2   >