Colin Percival
2014-10-11 00:29:53 UTC
Hi all,
I have just tagged the spiped-1.4.2 source tree and uploaded the release
tarball to the http://www.tarsnap.com/spiped.html . The SHA256 hash of
the release tarball is
dcb668f98a6bd761ff542f7079034f828f792259300eeb16aab53b687a805bde
This is a minor update to 1.4.1 and has just one significant change: When
AESNI is used, the round keys are correctly aligned on 16-byte boundaries,
even on platforms which do not provide this alignment automatically for
large allocations. Without this bug, spiped (and spipe) will crash on the
affected platforms.
Thanks to Denis Krienbuhl for reporting the bug and testing the fix.
- --
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
I have just tagged the spiped-1.4.2 source tree and uploaded the release
tarball to the http://www.tarsnap.com/spiped.html . The SHA256 hash of
the release tarball is
dcb668f98a6bd761ff542f7079034f828f792259300eeb16aab53b687a805bde
This is a minor update to 1.4.1 and has just one significant change: When
AESNI is used, the round keys are correctly aligned on 16-byte boundaries,
even on platforms which do not provide this alignment automatically for
large allocations. Without this bug, spiped (and spipe) will crash on the
affected platforms.
Thanks to Denis Krienbuhl for reporting the bug and testing the fix.
- --
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid