Hi Gary, I did a mvn clean test install from master, and it worked OK on my Linux box. Then grabbed the snapshot from https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-crypto/1.1.0-SNAPSHOT/ (the latest), and ran the command to test it successfully:
$ java -cp commons-crypto-1.1.0-20200824.190246-21.jar org.apache.commons.crypto.Crypto Apache Commons Crypto 1.1.0-SNAPSHOT Native code loaded OK: 1.1.0-SNAPSHOT Native name: Apache Commons Crypto Native built: Aug 23 2020 OpenSSL library loaded OK, version: 0x1010107f OpenSSL library info: OpenSSL 1.1.1g 21 Apr 2020 Random instance created OK: org.apache.commons.crypto.random.OpenSslCryptoRandom@2a84aee7 Cipher AES/CTR/NoPadding instance created OK: org.apache.commons.crypto.cipher.OpenSslCipher@1fb3ebeb Additional OpenSSL_version(n) details: 1: compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-InlZB1/openssl-1.1.1g=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 2: built on: Tue Apr 21 14:30:52 2020 UTC 3: platform: debian-amd64 4: OPENSSLDIR: "/usr/lib/ssl" 5: ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Alas on my Windows box it failed, probably due to missing OpenSSL. >java -cp commons-crypto-1.1.0-20200824.190246-21.jar >org.apache.commons.crypto.Crypto Apache Commons Crypto 1.1.0-SNAPSHOT Native code loaded OK: 1.1.0-SNAPSHOT Native name: Apache Commons Crypto Native built: Aug 16 2020 Exception in thread "main" java.lang.UnsatisfiedLinkError: OpenSSL_version at org.apache.commons.crypto.OpenSslInfoNative.OpenSSL(Native Method) at org.apache.commons.crypto.Crypto.main(Crypto.java:144) And I don't dare to install anything on this box right now, as IT support is taking a bit longer to reply (it's a $work laptop) due to the lockdown. At least it appears to be working OK for Linux 64. Hope that helps Bruno On Monday, 24 August 2020, 1:53:12 am NZST, Gary Gregory <garydgreg...@gmail.com> wrote: Building the binaries can be tricky, be warned. The trickiest to validate are aarch64, arm, and artmhf. All help is welcome of course. A smoke test would be to make sure that the native code from the SNAPSHOT jar from our SNAPSHOT repo can be loaded, for example, by calling from the command line the class org.apache.commons.crypto.Crypto For example, on: Linux dfd13586af7a 4.19.76-linuxkit #1 SMP Tue May 26 11:42:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux java -cp target/classes org.apache.commons.crypto.Crypto should output: Apache Commons Crypto 1.1.0-SNAPSHOT Native code loaded OK: 1.1.0-SNAPSHOT Native name: Apache Commons Crypto Native built: Aug 23 2020 OpenSSL library loaded OK, version: 0x1000106f OpenSSL library info: OpenSSL 1.0.1f 6 Jan 2014 Random instance created OK: org.apache.commons.crypto.random.OpenSslCryptoRandom@355da254 Cipher instance created OK: org.apache.commons.crypto.cipher.OpenSslCipher@6ff3c5b5 Additional OpenSSL_version(n) details: 1: not available 2: compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM 3: built on: Tue Dec 4 20:09:18 UTC 2018 4: platform: debian-amd64 5: OPENSSLDIR: "/usr/lib/ssl" Gary On Sun, Aug 23, 2020 at 2:23 AM Bruno P. Kinoshita <ki...@apache.org> wrote: > Hi Gary, > > I might be able to test on Win64 and Linux64 this week. You mentioned > snapshots… what is the easiest way to test them? Run some code using the > code of the snapshots, or perhaps run the build+tests from a tag/commit? > > > Cheers > Bruno > > > > > > > On Sunday, 23 August 2020, 11:49:21 am NZST, Gary Gregory < > garydgreg...@gmail.com> wrote: > > > > > > Hi all, > > I intent on creating a release candidate for Commons Crypto soon. > > I pushed a snapshot today which contains native binaries for Windows 32 and > 64, Linux 32 and 64, Mac 64, and ARM and ARM HF. > > Please help testing these on whatever platforms you may have access to. > > Gary > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
