On Mon, Jul 01, 2019 at 10:04:28AM -0400, James Turner wrote: > On Sun, Jun 30, 2019 at 09:43:34PM -0700, Colin Percival wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Hi scrypt users and tarsnap alphatesters, > > > > I've just uploaded a tarball which may be (modulo version number update) > > release 1.3.0 of my scrypt file encryption utility. There have been a > > non-trivial number of changes in the build code since scrypt 1.2.1, so > > I'm hoping you guys can test this and make sure we haven't broken anything. > > > > I'm asking the tarsnap alphatest list to test scrypt too, because a lot of > > the changes in scrypt will be in the next tarsnap release -- so think of > > this > > as a head start on alphatesting the next version of tarsnap. As always, bug > > reports will receive bug bounties; no need to wait for the bug to appear in > > a > > tarsnap release. > > > > You can download the scrypt code at > > https://www.tarsnap.com/scrypt/scrypt-1.2.99.tgz > > and the tarball has SHA256 hash > > 3a15d1f434d07f17befc91a1d9f259a67032b35fe9f3407de599e6b456f076ed > > . You can also see the tree from which I rolled this almost-release at > > https://github.com/Tarsnap/scrypt if you find it useful to crawl through > > VCS history. > > > > Significant functional changes since 1.2.1: > > * In addition to the scrypt command-line utility, a library "libscrypt-kdf" > > can now be built and installed by passing the --enable-libscrypt-kdf > > option > > to configure. > > * On x86 CPUs which support them, RDRAND and SHA extensions are used to > > provide supplemental entropy and speed up hash computations respectively. > > > > There are also a variety of less visible changes: Minor bug and compiler > > warning fixes, improvements to the test suite, and some minor corrections > > to source code comments. > > > > Assuming nobody yells (or the yells are things I can fix quickly and easily) > > I'll roll the official scrypt 1.3.0 release some time in the second half of > > July. > > > > - -- > > Colin Percival > > Security Officer Emeritus, FreeBSD | The power to serve > > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > > > > I get the following build errors on OpenBSD -current. > > In file included from libcperciva/alg/sha256.c:7: > libcperciva/alg/sha256_shani.h:14: error: static or type qualifiers in > abstract declarator > libcperciva/alg/sha256_shani.h:15: error: static or type qualifiers in > abstract declarator > libcperciva/alg/sha256.c:13: error: static or type qualifiers in abstract > declarator > libcperciva/alg/sha256.c:14: error: static or type qualifiers in abstract > declarator > libcperciva/alg/sha256.c:14: error: static or type qualifiers in abstract > declarator > libcperciva/alg/sha256.c:15: error: static or type qualifiers in abstract > declarator > gmake[1]: *** [Makefile:1114: libcperciva/alg/sha256.o] Error 1 > gmake[1]: Leaving directory '/home/james/scrypt-1.2.99' > gmake: *** [Makefile:694: all] Error 2 >
I should have noted that was under gcc (GCC) 4.2.1 20070719. If I change CC to the default clang, everything compiles just fine under OpenBSD. -- James Turner
