Trying to install openssl.org on Tru64

[Robert Walker_8]

Hi,

We use openssl.org and SSH from openssh.org.

Normally things havent been a problem, however it would seem that after 0.9.8i problems start to exist.

Normally on Tru64 can get away with

./config --prefix=/usr/local --openssldir=/usr/local/openssl shared

However now seem to have install problems with FIPS.

cp: fipscanister.o: No such file or directory

Robert.

[Steven Schweda]

Could you clarify exactly what you're
building how? OpenSSL some_version?
OpenSSH some_version, using OpenSSL
some_version? Actual commands?

And what did you do before which did work?

[Robert Walker_8]

Gday,

The problem I have is with openssl-0.9.8j (0.9.8i seems to work ok the way i normally build it as below)

# ./config --prefix=/usr/local --openssldir=/usr/local/openssl shared
# make
# make test (tests ok no errors)
# make install
(generates the last lines below)
making install in crypto/pem...
making install in crypto/x509...
making install in crypto/x509v3...
making install in crypto/conf...
making install in crypto/txt_db...
making install in crypto/pkcs7...
making install in crypto/pkcs12...
making install in crypto/comp...
making install in crypto/ocsp...
making install in crypto/ui...
making install in crypto/krb5...
making install in crypto/store...
making install in crypto/pqueue...
making install in fips...
making install in fips/sha...
making install in fips/rand...
making install in fips/des...
making install in fips/aes...
making install in fips/dsa...
making install in fips/rsa...
making install in fips/dh...
making install in fips/hmac...
cp: fipscanister.o: No such file or directory
cp: fipscanister.o.sha1: No such file or directory
*** Exit 1
Stop.
*** Exit 1
Stop.

I have tried options such as no-fips but this didnt work and articles I have found suggest no doing that anyway.

Robert.

[BFCsaus]

Hi, have you tried the precompiled openssl package from the writtenword.com ..??.. Its a setld install so pretty straight forward.

[Steven Schweda]

Around here, it fails using Tru64 "make", but
works using GNU "make". Well, it still
complains, but no one seems to care:

[...]
making install in fips/hmac...
gmake[2]: Entering directory `/usr/local/src/openssl/openssl-0.9.8j/fips/hmac'
gmake[2]: Leaving directory `/usr/local/src/openssl/openssl-0.9.8j/fips/hmac'
cp: fipscanister.o: No such file or directory
cp: fipscanister.o.sha1: No such file or directory
gmake[1]: Leaving directory `/usr/local/src/openssl/openssl-0.9.8j/fips'
[...]

When building most open-source products these
days, I normally use GNU "tar" and GNU
"make", especially on Tru64, where the tools
tend to be old and tired (and unlikely ever
to change). Most developers use mostly GNU
tools, and it's easier to conform than to
argue. Especially when you're likely to be
given a candid (that is, depressing)
assessment of the tools you're using now.

A Google search for
openssl fipscanister.o
found, among (many) other things:

http://www.nabble.com/fipscanister-error--help-td21709487.html

Sometimes a Web search is not a waste of
time.

[Robert Walker_8]

Did a fair bit of searching of the web before here, but Steven your suggestion did pay off - used a nightly update rather than posted SSL on openssl.org

Robert.