author Mike Sullivan <Mike.Sullivan@Oracle.COM>
Mon, 11 Mar 2013 10:38:09 -0700
changeset 2520 ceec631e74d1
parent 763 45da4d38492e
child 1267 3d7359ef8168
child 2674 4801864231c8
permissions -rw-r--r--
Close of build 10.
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or
# See the License for the specific language governing permissions
# and limitations under the License.
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
# Copyright (c) 2009, 2012, Oracle and/or its affiliates. All rights reserved.

Build Layout

OpenSSL build is run four times. Once for regular dynamic 1.0.0 non-fips, once 
for static 1.0.0 bits to link with standalone wanboot binary, once for 0.9.8
fips-140, and once for 0.9.8 FIPS-140 canister (in the openssl-fips component)
needed to build 0.9.8 FIPS-140 certified libraries. All builds apart from 
static libraries for wanboot are done for 32 and 64 bits. So, in total, OpenSSL
is built seven times. OpenSSL for wanboot is only build on sparc.

See also comments in all the Makefiles for more information.

The non-fips Build.

The non-fips build is the main build of OpenSSL and includes the regular
binaries, libraries, man pages, and header files.


Give better defaults. See 6193522 for more information.

Make sure the HMAC_CTX_init(3) man page gets delivered. See 6546806 for
more information.

Force openssl to install man pages into man[1357]openssl instead of man[1357].

Patch which adds the pkcs11 engine. See also the pkcs11-engine/

Adds five Solaris specific configurations (both 32bit and 64bit for both sparc
and x86, plus 64bit sparc for wanboot) to Configure which are then explicitly
used by the Makefiles. Wanboot configuration is special in that it doesn't link
with libc and uses -xF=%all to put functions in separate sections, so that
unused code can be discarded.

Care should be taken if modifying this patch as changes to compile-time options
can change the ABI. One example of this is the use of RC4_INT vs RC4_CHAR.

Prevent build binaries having an unnecessary runpath (/lib).

Build with non-executable stacks and non-executable data (x86).

Modifies Makefile.shared so that libssl is built with -znodelete.

Adds a new "enginesdir" option to the Configure script which allows a user to
specify the engines directory.

Modifies engines/Makefile so that the devcrypto engine will be built in the
"engines" directory. 

Wanboot specific patches.
- modified Makefiles not to build in engines apps test tools
- not using vfprintf for error print in crypto/cryptlib.c
- not using ERR_load_DSO_strings() in crypto/err/err_all.c
- not using EVP_read_pw_string() in crypto/evp/evp_key.c
    - reading password is implemented in disabled DES library
- avoid select() in crypto/rand/rand_unix.c
- direct reading of IP to avoid sscanf() in crypto/x509v3/v3_utl.c
- using functions from libsock in e_os.h
- by-passing version of sparc detection in crypto/sparcv9cap.c
    - results in not using FPU for big numbers multiplication
    - should be ok - original detection seems broken, FPU gets never used
- implementation of atoi()

X86-only patch.
Add a built-in engine, aesni, to support X86 AES-NI instructions, along with
files engines/aesni/aesni-x86[_64].pl.
This patch is for OpenSSL 1.0.0d.  For newer OpenSSL versions, a newer patch
may be needed.

SPARC-only patch.
Add a built-in engine, t4, to support SPARC T4 crypto instructions.
along with files in directory engines/t4.

Modifies opensslconf.h so that it is suitable for both 32bit and 64bit installs.
OpenSSL either builds for 32bit or 64bit - it doesn't allow for combined 32bit
and 64bit builds.

The fips Build

FIPS-140 certified libraries for Solaris private use. We wait for OpenSSL 1.0.0
to be FIPS-140 certified in which time we can ship only 1.0.0 with S11 and make
it a public interface.


All the patches from 1.0.0 are used in 0.9.8 as well aside from
14-manpage_openssl.patch which is not needed since we do not deliver 0.9.8 man
pages. Additional patches:

Fixing a bug introduces in 0.9.8q and fixed in 0.9.8r.

Workaround so that fingerprinting the canister during runtime and comparing it
with the saved fingerprint works correctly.

The wanboot Build

There are some significant differences when building OpenSSL for wanboot.

Some additional Configuration options are needed:
-DNO_CHMOD		chmod not available in stand-alone environment
-DBOOT			guard for wanboot specific patches
-DOPENSSL_NO_DTLS1	to avoid dtls1_min_mtu() - DTLS not used anyway

List of object files for wanboot-openssl.o

At this moment, object files for wanboot-openssl.o need to be listed explicitly.
This is cumbersome and relatively tedious with respect to upgrading to higher
version of openssl. 

In future, it would be nice, if this could be performed automatically by the
linker. The required interface for wanboot is already defined in a mapfile and
linker option '-zdiscard-unused=sections,files' is already used to discard
unused code. 
But sadly, at this moment when the linker is given all the object files, it
correctly discards some unused files, but references to undefined symbols from
the discarded files don't get discarded along. Later, these undefined references
cause wanboot linking failure. 

In order to determine which openssl object files are required for wanboot,
first build static standalone openssl bits in Userland. As a site effect,
static libraries libssl.a and libcrypto.a are created in build/sparcv9-wanboot.

    $ cd $USERLAND/components/openssl/openssl-1.0.0 ; gmake build

Next, collect some information from linking wanboot static libraries in ON.
This can be done by the following hack.

    $ cd $ON/usr/src/psm/stand/boot/sparcv9/sun4
    $ touch wanboot.o
    $ LD_OPTIONS="-Dfiles,symbols,output=ld.dbg \
        -L$USERLAND/components/openssl/openssl-1.0.0/build/sparcv9-wanboot " \
        WAN_OPENSSL=" -lwanboot -lssl -lcrypto" dmake all

The following sort of information ends up in ld.dbg (note that the debugging
output from the link-editor is not considered a 'stable interface' and may
change in the future):

    debug: file=/builds/tkuthan/ul-wanboot-rebuilt/components/openssl/openssl-1.0.0/build/sparcv9-wanboot/libcrypto.a(sparcv9cap.o)  [ ET_REL ]
    debug: symbol table processing; file=/builds/tkuthan/ul-wanboot-rebuilt/components/openssl/openssl-1.0.0/build/sparcv9-wanboot/libcrypto.a(sparcv9cap.o)  [ ET_REL ]
    debug: symbol[1]=sparcv9cap.c

Now run the following script in Userland:

    # set to workspace paths:
    for i in `find $BUILD/crypto $BUILD/ssl -name '*.o'`
            f=`basename $i`
            if grep -q "^debug: file.*\<$f\>" $LD_DBG
                    echo $i | sed "s#$BUILD/##"

to get the list of required object files.

Additionally, you can format the list for including to Makefile by:
    sort | tr '\n' ' ' | fold -s -w74 | sed -e 's/^/    /' -e 's/$/\\/'

Linking with wanboot

When linking with wanboot please pay attention to following pitfalls.

Correct openssl header files need to be included. This is done in
Make sure CPPFLAGS point to the right directories.

EXTREME CAUTION needs to be employed, if WANBOOT GREW IN SIZE because of the
Wanboot is a statically linked standalone binary and it is loaded on a fixed
address before execution. This address is defined in 

     27 LOAD_SEGMENT text {
     29 	VADDR = 0x130000;
     31 		TYPE = PROGBITS;
     32 		FLAGS = ALLOC !WRITE;
     33 	};
     34 };

    size of wanboot binary + 0x4000

The reason for this is in how wanboot is loaded by OpenBoot Prom:
1) user initiates boot from network - "boot net"
2) obp loads wanboot binary at address 0x4000
3) obp parses ELF header, reads virtual address where to load wanboot to
4) obp mem-copies .text section to this address
5) obp copies .data section behind .text
6) obp starts executing wanboot at entry address

If the given address is too small, obp overwrites part of .data with
instructions from .text in step 4. resulting in .data being corrupted.
Initialized variables get bogus values and failure is inevitable.
This is very hard to troubleshoot.

Testing wanboot with new openssl

With every upgrade of OpenSSL, it is necessary to make sure wanboot builds and
works well with the new bits.

Provided you have a freshly built ON workspace, you can link wanboot with new
OpenSSL bits by redefining WAN_OPENSSL macro:

    # copy wanboot-openssl.o to ON build machine
    cp wanboot-openssl.o /var/tmp/

    # prepare to rebuild wanboot
    cd $ON
    cd usr/src/psm/stand/boot/sparcv9/sun4

    # hack to force a rebuild
    touch wanboot.o

    # link new OpenSSL to wanboot
    WAN_OPENSSL=/var/tmp/wanboot-openssl.o dmake all

Wanboot should build without warning.

If there is something like this in the output:

    Undefined                       first referenced
     symbol                             in file
    CRYPTO_ccm128_setiv                 /var/tmp/wanboot-openssl.o
    SSL_get_srtp_profiles               /var/tmp/wanboot-openssl.o
    ssl_parse_clienthello_use_srtp_ext  /var/tmp/wanboot-openssl.o
    CRYPTO_gcm128_setiv                 /var/tmp/wanboot-openssl.o
    cmac_pkey_meth                      /var/tmp/wanboot-openssl.o
    ld: fatal: symbol referencing errors. No output written to wanboot
    *** Error code 1
    dmake: Fatal error: Command failed for target `wanboot'

some additional work has to be done in OpenSSL to either satisfy the function 
references listed in the linker error message, or to remove the calls to these

Finally, resulting wanboot binary shall be deployed on some install server and
wanbooting from this server shall be tested.