On 9 Oct 2009, at 21:43, Colin Percival wrote:
James Montgomerie wrote:On 9 Oct 2009, at 20:30, Colin Percival wrote:James Montgomerie wrote:tarsnap-keygen: error in AES_set_encrypt_keyWow, that's a weird error -- that's an OpenSSL function which is failing, andthere's really no good reason why it should ever fail. Can you checkwhich version of OpenSSL you have installed?[~/admin] things$ openssl version OpenSSL 0.9.8k 25 Mar 2009Ok, google tells me that for some dumb reason Solaris ships with a version of OpenSSL without support for AES-256 (and that lots of other people are getting irritated with this). Can you check which version of OpenSSL the tarsnap binaries are linked to? (On BSD, `ldd tarsnap-keygen` will do this -- I'm notsure if it's the same command on Solaris.)My guess is that you have two versions of OpenSSL installed and tarsnap is beinglinked to the broken one which came with Solaris.
Yes - you're correct! There's a version of openssl in /usr/sfw which is what was being linked to. I manually edited the post-cofigure Makefile to use /usr/local in place of /usr/sfw everywhere, recompiled, and tarsnap-keygen ran successfully.
I'm no autoconf expoert, so I'm not quite sure where /usr/sfw is being picked up from. I did take a look at the logs, but the only thing that jumped out to me was that gcc is also installed in /usr/sfw. I can supply the config.log (or even a tarball of the complete post-make source directory) if that would be useful to you?
Anyway, I'm happy now - my first tarsnap backup is underway as I type. Thanks for all the help!
Jamie.