{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"", "gen_ut":1757459159, "reponame":"openssl", "desc":"OpenSSL", "owner": { "name": "Andy Green", "email": "andy@warmcat.com", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"https://warmcat.com/repo/openssl", "f":3, "items": [ {"schema":"libjg2-1", "cid":"d4cec989faab3322d6badb36eaa92886", "oid":{ "oid": "81161070f8ec75ba83964e98ad70c4c4d015c276", "alias": []},"blobname": "INSTALL", "blob": "\n OPENSSL INSTALLATION\n --------------------\n\n [Installation on DOS (with djgpp), MacOS (before MacOS X)\n and NetWare is described in INSTALL.DJGPP, INSTALL.MacOS\n and INSTALL.NW.\n \n This document describes installation on the main supported operating\n systems, currently the Linux/Unix family, OpenVMS and Windows.]\n\n To install OpenSSL, you will need:\n\n * make\n * Perl 5 with core modules (please read README.PERL)\n * The perl module Text::Template (please read README.PERL)\n * an ANSI C compiler\n * a development environment in the form of development libraries and C\n header files\n * a supported operating system\n\n For more details regarding specific platforms, there are these notes\n available:\n\n * NOTES.VMS (OpenVMS)\n * NOTES.WIN (any Windows except for Windows CE)\n\n Quick Start\n -----------\n\n If you want to just get on with it, do:\n\n on Unix:\n\n $ ./config\n $ make\n $ make test\n $ make install\n\n on OpenVMS:\n\n $ @config\n $ mms\n $ mms test\n $ mms install\n\n on Windows (only pick one of the targets for configuration):\n\n $ perl Configure { VC-WIN32 | VC-WIN64A | VC-WIN64I | VC-CE }\n $ nmake\n $ nmake test\n\n [If any of these steps fails, see section Installation in Detail below.]\n\n This will build and install OpenSSL in the default location, which is:\n\n Unix: normal installation directories under /usr/local\n OpenVMS: SYS$COMMON:[OPENSSL-'version'...], where 'version' is the\n OpenSSL version number ('major'_'minor').\n Windows: currently don't have an install function \u003cTBA\u003e\n\n If you want to install it anywhere else, run config like this:\n\n On Unix:\n\n $ ./config --prefix\u003d/opt/openssl --openssldir\u003d/usr/local/ssl\n\n On OpenVMS:\n\n $ @config --prefix\u003dPROGRAM:[INSTALLS] --openssldir\u003dSYS$MANAGER:[OPENSSL]\n\n\n Configuration Options\n ---------------------\n\n There are several options to ./config (or ./Configure) to customize\n the build:\n\n --prefix\u003dDIR The top of the installation directory tree. Defaults are:\n\n Unix: /usr/local\n OpenVMS: SYS$COMMON:[OPENSSL-'version']\n\n --openssldir\u003dDIR Directory for OpenSSL configuration files, and also the\n default certificate and key store. Defaults are:\n\n Unix: PREFIX/ssl (PREFIX is given by --prefix)\n OpenVMS: SYS$COMMON:[SSL]\n\n --api\u003dx.y.z Don't build with support for deprecated APIs below the\n specified version number. For example \u0022--api\u003d1.1.0\u0022 will\n remove support for all APIS that were deprecated in OpenSSL\n version 1.1.0 or below.\n\n no-deprecated Don't build with support for any deprecated APIs. This is the\n same as using \u0022--api\u0022 and supplying the latest version\n number.\n\n no-autoalginit Don't automatically load all supported ciphers and digests.\n Typically OpenSSL will make available all of its supported\n ciphers and digests. For a statically linked application this\n may be undesirable if small executable size is an objective.\n This only affects libcrypto. Ciphers and digests will have to\n be loaded manually using EVP_add_cipher() and\n EVP_add_digest() if this option is used.\n\n no-autoerrinit Don't automatically load all libcrypto/libssl error strings.\n Typically OpenSSL will automatically load human readable\n error strings. For a statically linked application this may\n be undesirable if small executable size is an objective.\n\n no-threads Don't try to build with support for multi-threaded\n applications.\n\n threads Build with support for multi-threaded applications.\n This will usually require additional system-dependent\n options! See \u0022Note on multi-threading\u0022 below.\n\n no-zlib Don't try to build with support for zlib compression and\n decompression.\n\n zlib Build with support for zlib compression/decompression.\n\n zlib-dynamic Like \u0022zlib\u0022, but has OpenSSL load the zlib library\n dynamically when needed. This is only supported on systems\n where loading of shared libraries is supported. This is the\n default choice.\n\n no-shared Don't try to create shared libraries.\n\n shared In addition to the usual static libraries, create shared\n libraries on platforms where it's supported. See \u0022Note on\n shared libraries\u0022 below.\n\n no-asm Do not use assembler code.\n\n 386 On Intel hardware, use the 80386 instruction set only\n (the default x86 code is more efficient, but requires at\n least a 486). Note: Use compiler flags for any other CPU\n specific configuration, e.g. \u0022-m32\u0022 to build x86 code on\n an x64 system.\n\n no-sse2 Exclude SSE2 code pathes. Normally SSE2 extension is\n detected at run-time, but the decision whether or not the\n machine code will be executed is taken solely on CPU\n capability vector. This means that if you happen to run OS\n kernel which does not support SSE2 extension on Intel P4\n processor, then your application might be exposed to\n \u0022illegal instruction\u0022 exception. There might be a way\n to enable support in kernel, e.g. FreeBSD kernel can be\n compiled with CPU_ENABLE_SSE, and there is a way to\n disengage SSE2 code pathes upon application start-up,\n but if you aim for wider \u0022audience\u0022 running such kernel,\n consider no-sse2. Both 386 and no-asm options above imply\n no-sse2.\n\n no-\u003calg\u003e Build without the specified algorithm (bf, cast, des, dh,\n dsa, hmac, md2, md5, mdc2, rc2, rc4, rc5, rsa, sha).\n\n -Dxxx, -lxxx, These system specific options will be passed through to the\n -Lxxx, -fxxx, compiler to allow you to define preprocessor symbols, specify\n -mXXX, -Kxxx additional libraries, library directories or other compiler\n options.\n\n\n Installation in Detail\n ----------------------\n\n 1a. Configure OpenSSL for your operation system automatically:\n\n NOTE: This is not available on Windows.\n\n $ ./config [options] # Unix\n\n or\n\n $ @config [options] ! OpenVMS\n\n For the remainder of this text, the Unix form will be used in all\n examples, please use the appropriate form for your platform.\n\n This guesses at your operating system (and compiler, if necessary) and\n configures OpenSSL based on this guess. Run ./config -t to see\n if it guessed correctly. If you want to use a different compiler, you\n are cross-compiling for another platform, or the ./config guess was\n wrong for other reasons, go to step 1b. Otherwise go to step 2.\n\n On some systems, you can include debugging information as follows:\n\n $ ./config -d [options]\n\n 1b. Configure OpenSSL for your operating system manually\n\n OpenSSL knows about a range of different operating system, hardware and\n compiler combinations. To see the ones it knows about, run\n\n $ ./Configure # Unix\n\n or\n\n $ perl Configure # All other platforms\n\n For the remainder of this text, the Unix form will be used in all\n examples, please use the appropriate form for your platform.\n\n Pick a suitable name from the list that matches your system. For most\n operating systems there is a choice between using \u0022cc\u0022 or \u0022gcc\u0022. When\n you have identified your system (and if necessary compiler) use this name\n as the argument to Configure. For example, a \u0022linux-elf\u0022 user would\n run:\n\n $ ./Configure linux-elf [options]\n\n If your system isn't listed, you will have to create a configuration\n file named Configurations/{something}.conf and add the correct\n configuration for your system. See the available configs as examples\n and read Configurations/README and Configurations/README.design for\n more information.\n\n The generic configurations \u0022cc\u0022 or \u0022gcc\u0022 should usually work on 32 bit\n Unix-like systems.\n\n Configure creates a build file (\u0022Makefile\u0022 on Unix and \u0022descrip.mms\u0022\n on OpenVMS) from a suitable template in Configurations, and\n defines various macros in crypto/opensslconf.h (generated from\n crypto/opensslconf.h.in).\n\n 1c. Configure OpenSSL for building outside of the source tree.\n\n OpenSSL can be configured to build in a build directory separate from\n the directory with the source code. It's done by placing yourself in\n some other directory and invoking the configuration commands from\n there.\n\n Unix example:\n\n $ mkdir /var/tmp/openssl-build\n $ cd /var/tmp/openssl-build\n $ /PATH/TO/OPENSSL/SOURCE/config [options]\n\n or\n\n $ /PATH/TO/OPENSSL/SOURCE/Configure [target] [options]\n\n OpenVMS example:\n\n $ set default sys$login:\n $ create/dir [.tmp.openssl-build]\n $ set default [.tmp.openssl-build]\n $ @[PATH.TO.OPENSSL.SOURCE]config {options}\n\n or\n\n $ @[PATH.TO.OPENSSL.SOURCE]Configure {target} {options}\n\n Windows example:\n\n $ C:\n $ mkdir \u005ctemp-openssl\n $ cd \u005ctemp-openssl\n $ perl d:\u005cPATH\u005cTO\u005cOPENSSL\u005cSOURCE\u005cConfigure {target} {options}\n\n Paths can be relative just as well as absolute. Configure will\n do its best to translate them to relative paths whenever possible.\n\n 2. Build OpenSSL by running:\n\n $ make # Unix\n $ mms ! (or mmk) OpenVMS\n $ nmake # Windows\n\n This will build the OpenSSL libraries (libcrypto.a and libssl.a on\n Unix, corresponding on other platforms) and the OpenSSL binary\n (\u0022openssl\u0022). The libraries will be built in the top-level directory,\n and the binary will be in the \u0022apps\u0022 subdirectory.\n\n If the build fails, look at the output. There may be reasons for\n the failure that aren't problems in OpenSSL itself (like missing\n standard headers). If it is a problem with OpenSSL itself, please\n report the problem to \u003crt@openssl.org\u003e (note that your message\n will be recorded in the request tracker publicly readable at\n https://www.openssl.org/community/index.html#bugs and will be\n forwarded to a public mailing list). Please check out the request\n tracker. Maybe the bug was already reported or has already been\n fixed.\n\n [If you encounter assembler error messages, try the \u0022no-asm\u0022\n configuration option as an immediate fix.]\n\n Compiling parts of OpenSSL with gcc and others with the system\n compiler will result in unresolved symbols on some systems.\n\n 3. After a successful build, the libraries should be tested. Run:\n\n $ make test # Unix\n $ mms test ! OpenVMS\n $ nmake test # Windows\n\n If some tests fail, look at the output. There may be reasons for\n the failure that isn't a problem in OpenSSL itself (like a\n malfunction with Perl). You may want increased verbosity, that\n can be accomplished like this:\n\n $ HARNESS_VERBOSE\u003dyes make test # Unix\n\n $ DEFINE HARNESS_VERBOSE YES\n $ mms test ! OpenVMS\n\n $ set HARNESS_VERBOSE\u003dyes\n $ nmake test # Windows\n\n If you want to run just one or a few specific tests, you can use\n the make variable TESTS to specify them, like this:\n\n $ make TESTS\u003d'test_rsa test_dsa' test # Unix\n $ mms/macro\u003d\u0022TESTS\u003dtest_rsa test_dsa\u0022 test ! OpenVMS\n $ nmake TESTS\u003d'test_rsa test_dsa' test # Windows\n\n And of course, you can combine (Unix example shown):\n \n $ HARNESS_VERBOSE\u003dyes make TESTS\u003d'test_rsa test_dsa' test\n\n You can find the list of available tests like this:\n\n $ make list-tests # Unix\n $ mms list-tests ! OpenVMS\n $ nmake list-tests # Windows\n\n Have a look at the manual for the perl module Test::Harness to\n see what other HARNESS_* variables there are.\n\n If you find a problem with OpenSSL itself, try removing any\n compiler optimization flags from the CFLAGS line in Makefile and\n run \u0022make clean; make\u0022 or corresponding.\n\n Please send a bug reports to \u003crt@openssl.org\u003e.\n\n 4. If everything tests ok, install OpenSSL with\n\n $ make install # Unix\n $ mms install ! OpenVMS\n\n This will install all the software components in this directory\n tree under PREFIX (the directory given with --prefix or its\n default):\n\n Unix:\n\n bin/ Contains the openssl binary and a few other\n utility scripts.\n include/openssl\n Contains the header files needed if you want\n to build your own programs that use libcrypto\n or libssl.\n lib Contains the OpenSSL library files.\n lib/engines Contains the OpenSSL dynamically loadable engines.\n share/man/{man1,man3,man5,man7}\n Contains the OpenSSL man-pages.\n share/doc/openssl/html/{man1,man3,man5,man7}\n Contains the HTML rendition of the man-pages.\n\n OpenVMS ('arch' is replaced with the architecture name, \u0022Alpha\u0022\n or \u0022ia64\u0022):\n\n [.EXE.'arch'] Contains the openssl binary and a few other\n utility scripts.\n [.include.openssl]\n Contains the header files needed if you want\n to build your own programs that use libcrypto\n or libssl.\n [.LIB.'arch'] Contains the OpenSSL library files.\n [.ENGINES.'arch']\n Contains the OpenSSL dynamically loadable engines.\n [.SYS$STARTUP] Contains startup, login and shutdown scripts.\n These define appropriate logical names and\n command symbols.\n \n\n Additionally, install will add the following directories under\n OPENSSLDIR (the directory given with --openssldir or its default)\n for you convenience:\n\n certs Initially empty, this is the default location\n for certificate files.\n private Initially empty, this is the default location\n for private key files.\n misc Various scripts.\n\n Package builders who want to configure the library for standard\n locations, but have the package installed somewhere else so that\n it can easily be packaged, can use\n\n $ make DESTDIR\u003d/tmp/package-root install # Unix\n $ mms/macro\u003d\u0022DESTDIR\u003dTMP:[PACKAGE-ROOT]\u0022 install ! OpenVMS\n\n The specified destination directory will be prepended to all\n installation target paths.\n\n Compatibility issues with previous OpenSSL versions:\n\n * COMPILING existing applications\n\n OpenSSL 1.1 hides a number of structures that were previously\n open. This includes all internal libssl structures and a number\n of EVP types. Accessor functions have been added to allow\n controlled access to the structures' data.\n\n This means that some software needs to be rewritten to adapt to\n the new ways of doing things. This often amounts to allocating\n an instance of a structure explicitly where you could previously\n allocate them on the stack as automatic variables, and using the\n provided accessor functions where you would previously access a\n structure's field directly.\n\n \u003cTBA\u003e\n\n Some APIs have changed as well. However, older APIs have been\n preserved when possible.\n\n\n Note on multi-threading\n -----------------------\n\n For some systems, the OpenSSL Configure script knows what compiler options\n are needed to generate a library that is suitable for multi-threaded\n applications. On these systems, support for multi-threading is enabled\n by default; use the \u0022no-threads\u0022 option to disable (this should never be\n necessary).\n\n On other systems, to enable support for multi-threading, you will have\n to specify at least two options: \u0022threads\u0022, and a system-dependent option.\n (The latter is \u0022-D_REENTRANT\u0022 on various systems.) The default in this\n case, obviously, is not to include support for multi-threading (but\n you can still use \u0022no-threads\u0022 to suppress an annoying warning message\n from the Configure script.)\n\n OpenSSL provides built-in support for two threading models: pthreads (found on\n most UNIX/Linux systems), and Windows threads. No other threading models are\n supported. If your platform does not provide pthreads or Windows threads then\n you should Configure with the \u0022no-threads\u0022 option.\n\n Note on shared libraries\n ------------------------\n\n Shared libraries have certain caveats. Binary backward compatibility\n can't be guaranteed before OpenSSL version 1.0. The only reason to\n use them would be to conserve memory on systems where several programs\n are using OpenSSL.\n\n For most systems, the OpenSSL Configure script knows what is needed to\n build shared libraries for libcrypto and libssl. On these systems,\n the shared libraries are currently not created by default, but giving\n the option \u0022shared\u0022 will get them created.\n\n Note on random number generation\n --------------------------------\n\n Availability of cryptographically secure random numbers is required for\n secret key generation. OpenSSL provides several options to seed the\n internal PRNG. If not properly seeded, the internal PRNG will refuse\n to deliver random bytes and a \u0022PRNG not seeded error\u0022 will occur.\n On systems without /dev/urandom (or similar) device, it may be necessary\n to install additional support software to obtain random seed.\n Please check out the manual pages for RAND_add(), RAND_bytes(), RAND_egd(),\n and the FAQ for more information.\n\n","s":{"c":1757459159,"u": 997}} ],"g": 7112,"chitpc": 0,"ehitpc": 0,"indexed":0 , "ab": 1, "si": 0, "db":0, "di":0, "sat":0, "lfc": "0000"}