aboutsummaryrefslogtreecommitdiffstats
path: root/Makefile.org
Commit message (Collapse)AuthorAgeFilesLines
* Patches from Vern Staats <staatsvr@asc.hpc.mil> to get Kerberos 5 inRichard Levitte2001-07-091-2/+2
| | | | | | | | | | | | | | | | SSL according to RFC 2712. His comment is: This is a patch to openssl-SNAP-20010702 to support Kerberized SSL authentication. I'm expecting to have the full kssl-0.5 kit up on sourceforge by the end of the week. The full kit includes patches for mod-ssl, apache, and a few text clients. The sourceforge URL is http://sourceforge.net/projects/kssl/ . Thanks to a note from Simon Wilkinson I've replaced my KRB5 AP_REQ message with a real KerberosWrapper struct. I think this is fully RFC 2712 compliant now, including support for the optional authenticator field. I also added openssl-style ASN.1 macros for a few Kerberos structs; see crypto/krb5/ if you're interested.
* Small detail about AIX forgotten...Richard Levitte2001-06-051-2/+2
|
* Add a general user interface API. This is designed to replace thingsRichard Levitte2001-05-061-1/+1
| | | | | | | like des_read_password and friends (backward compatibility functions using this new API are provided). The purpose is to remove prompting functions from the DES code section as well as provide for prompting through dialog boxes in a window system and the like.
* A method to create shared libraries on AIX, and according toRichard Levitte2001-04-271-0/+43
| | | | | "Howard Chu" <hyc@highlandsun.com>, it may be general enough to work on any Unixly system.
* Linux shared libraries can be linked with debug symbols.Richard Levitte2001-04-261-2/+2
| | | | Tru64 shared libraries can be linked with static libraries.
* undo previous change ...Bodo Möller2001-04-121-2/+0
|
* update from 0.9.6aBodo Möller2001-04-121-0/+2
|
* '||', '&&' and 'test -x' apparently don't work on Ultrix;Bodo Möller2001-04-081-2/+2
| | | | also 'test' appears to be available as '[' only in 'if' conditions.
* Incorporate some changes that make OpenSSL compilable in CygWin.Richard Levitte2001-04-041-3/+4
|
* Make do_bsd-gcc-shared depend on do_gnu-shared instead of the non-existent ↵Richard Levitte2001-04-041-1/+1
| | | | linux-shared
* When using the native tools on Solaris, make damn sure the native ldRichard Levitte2001-03-241-1/+2
| | | | is used, even if the user has GNU ld earlier in his $PATH.
* ln on Solaris expects -f to come before -s.Richard Levitte2001-03-241-2/+3
| | | | | The linux-shared method is actually gcc-specific, so call it gnu-shared as well.
* We really have no need for PEX_LIBS, so empty it.Richard Levitte2001-03-221-1/+1
|
* Minimise the amount of -L. when linking the shared libraries. ItRichard Levitte2001-03-151-9/+9
| | | | seems like some Unixen (SCO) have opinions about too many -L.
* typoBodo Möller2001-03-131-1/+1
|
* Forcibly enable memory leak checking during "make test"Bodo Möller2001-03-111-2/+2
|
* Change obj_... generation so that it does not generate rubbish orBodo Möller2001-03-061-2/+2
| | | | | | | | abort with errors if no name is defined for some object, which was the case for 'pilotAttributeType 27'. Also avoid this very situation by assigning the name 'pilotAttributeType27'.
* Move ec.h to ec2.h because it is not compatible with what we will use.Bodo Möller2001-03-051-1/+1
| | | | | | | Add EC vaporware: change relevant Makefiles and add some empty source files. "make update".
* e_os.h does not belong with the exported headers. Do not put it thereRichard Levitte2001-02-221-2/+9
| | | | | | | | and make all files the depend on it include it without prefixing it with openssl/. This means that all Makefiles will have $(TOP) as one of the include directories.
* Make all configuration macros available for application by makingRichard Levitte2001-02-191-3/+5
| | | | | | | | | | | | sure they are available in opensslconf.h, by giving them names starting with "OPENSSL_" to avoid conflicts with other packages and by making sure e_os2.h will cover all platform-specific cases together with opensslconf.h. I've checked fairly well that nothing breaks with this (apart from external software that will adapt if they have used something like NO_KRB5), but I can't guarantee it completely, so a review of this change would be a good thing.
* Pass ${PERL} down to the Makefile in sub-directory "test" inBodo Möller2001-01-101-1/+1
| | | | "make tests"
* Use $(PERL) in place of hard-coded perlBodo Möller2001-01-101-7/+7
|
* First tentative impementation of Kerberos 5 cryptos and keys for SSL/TLS. ↵Richard Levitte2000-11-301-3/+7
| | | | Implemented by Vern Staats <staatsvr@asc.hpc.mil>, further hacked and distributed by Jeffrey Altman <jaltnab@columbia.edu>
* Some platforms (namely HP-UX) require the 'x' bit set for shared libraries.Lutz Jänicke2000-11-141-2/+2
| | | | | | | | | For performance reasons, it is also recommended to make the (mmap'ed) shared library 'read-only'. -> New permissions for installed shared libraries = 555 This doesn't hurt anybody, provided the installation is performed with 'cp -f' :-)
* HP-UX shared libraries do not build any longer, as EX_LIBS containsLutz Jänicke2000-11-131-8/+26
| | | | | | | | | | | | | | "-Wl,+s" instead of +s: * Hardcoded necessary references to -ldld/-ldl into the build rules and removed EX_LIBS. HP-UX records the pathnames of dependent libraries when the shared libs are built, so that ./libcrypto.sl... is recorded in libssl.sl..., with "./" not being resolvable when running an application linked against -lssl: * Build libssl without explicit reference to libcrypto, applications will be linked with "-lssl -lcrypto" anyway. Document these informations in Makefile.org.
* For a long time, I've wanted to be able to easily run one or a fewRichard Levitte2000-11-121-1/+5
| | | | individual tests. I finally got myself to implement it...
* Remove references to RSAref. The glue library is but a memory to fadeRichard Levitte2000-11-081-2/+1
| | | | away now...
* Make sure that shared libraries get the internal name engine with theRichard Levitte2000-11-061-3/+3
| | | | | | full version number and not just 0. This should mark the shared libraries as not backward compatible. Of course, this should be changed again when we can guarantee backward binary compatibility.
* Add support for shared libraries under Irix.Richard Levitte2000-11-011-0/+9
| | | | Submitted by Albert Chin-A-Young <china@thewrittenword.com>
* Rename true64 to the correct tru64.Richard Levitte2000-10-311-1/+1
| | | | Suggested by Albert Chin-A-Young <china@thewrittenword.com>
* The majority of the OCSP code from CertCo.Richard Levitte2000-10-271-1/+1
|
* Merge the engine branch into the main trunk. All conflicts resolved.Richard Levitte2000-10-261-1/+1
| | | | At the same time, add VMS support for Rijndael.
* When building shared libraries on HP-UX 10.20 and HP-UX 11.00 (32bit),Richard Levitte2000-10-221-1/+2
| | | | | | ld warns that -Fl "may not be supported in future releases". We know that, and are doing things in HP-UX 11 (64bit), so turn off that warning with +vnocompatwarnings.
* It seems like grep isn't as capable as I thought on some Unix systems.Richard Levitte2000-10-221-1/+1
| | | | Use egrep instead.
* Add what's needed to get shared libraries on HP-UX.Richard Levitte2000-10-211-0/+18
| | | | N.B.: This has not been tested at all, that's my next step.
* The experimental Rijndael code moved to the main trunk.Richard Levitte2000-10-141-1/+1
| | | | make update done.
* Rework the system to generate shared libraries:Richard Levitte2000-10-131-82/+72
| | | | | | | | | | | | | | - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
* Make sure ranlib is only used on .a libraries.Richard Levitte2000-10-091-1/+2
|
* Verbose output when installing manual pages so that you see thatBodo Möller2000-09-261-2/+2
| | | | something is going on (and what).
* I'm using GNU tar...Richard Levitte2000-09-211-1/+1
|
* Allow reconfiguration. This can be useful if some source updateRichard Levitte2000-08-171-0/+1
| | | | | requires that you configure again, but you don't want to reenter all those configuration arguments again.
* MD4 implemented. Assar Westerlund provided the digest code itself and the ↵Richard Levitte2000-08-141-1/+1
| | | | test utility, I added the bits to get a EVP interface, the command line utility and the speed test
* It's probably a good idea to make the shared libraries depend in EX_LIBS.Richard Levitte2000-08-021-3/+3
|
* A few corrections with the shared library support:Richard Levitte2000-08-021-13/+10
| | | | | | 1. make sure libssl.so becomes dependent on libcrypto.so 2. correct a number of silly bugs in the solaris-shared target, and make sure lib*.so also depends on libc.so.
* Add support for solaris shared libraries, currently just experimentalRichard Levitte2000-07-241-0/+18
| | | | (there's no way to get it through configuration yet).
* Avoid loops, and make sure that it's possible to still build sharedRichard Levitte2000-07-241-4/+12
| | | | libraries even if the "shared" configuration option wasn't chosen.
* Redo and enhance the support for building shared libraries. CurrentlyRichard Levitte2000-07-211-45/+125
| | | | | | | | | | | | | | | | | | | | | there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
* I got sick and tired of having to keep track of NIDs when such a thingRichard Levitte2000-07-051-2/+4
| | | | | | | | | | | | | | | | | | could be done automagically, much like the numbering in libeay.num and ssleay.num. The solution works as follows: - New object identifiers are inserted in objects.txt, following the syntax given in objects.README. - objects.pl is used to process obj_mac.num and create a new obj_mac.h. - obj_dat.pl is used to create a new obj_dat.h, using the data in obj_mac.h. This is currently kind of a hack, and the perl code in objects.pl isn't very elegant, but it works as I intended. The simplest way to check that it worked correctly is to look in obj_dat.h and check the array nid_objs and make sure the objects haven't moved around (this is important!). Additions are OK, as well as consistent name changes.
* Using speaking "variable" names in macros so that e.g. grepping forBodo Möller2000-06-171-1/+1
| | | | | | | | sk_whatever_insert and sk_whatever_set immediately reveals the subtle difference in parameter order. Change mkstack.pl so that safestack.h is not rewritten when nothing has changed.
* This change will cause builds (by default) to not use different STACKGeoff Thorpe2000-06-011-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | structures and functions for each stack type. The previous behaviour can be enabled by configuring with the "-DDEBUG_SAFESTACK" option. This will also cause "make update" (mkdef.pl in particular) to update the libeay.num and ssleay.num symbol tables with the number of extra functions DEBUG_SAFESTACK creates. The way this change works is to accompany each DECLARE_STACK_OF() macro with a set of "#define"d versions of the sk_##type##_*** functions that ensures all the existing "type-safe" stack calls are precompiled into the underlying stack calls. The presence or abscence of the DEBUG_SAFESTACK symbol controls whether this block of "#define"s or the DECLARE_STACK_OF() macro is taking effect. The block of "#define"s is in turn generated and maintained by a perl script (util/mkstack.pl) that encompasses the block with delimiting C comments. This works in a similar way to the auto-generated error codes and, like the other such maintenance utilities, is invoked by the "make update" target. A long (but mundane) commit will follow this with the results of "make update" - this will include all the "#define" blocks for each DECLARE_STACK_OF() statement, along with stripped down libeay.num and ssleay.num files.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-10 11:07:59 +0000