aboutsummaryrefslogtreecommitdiff
path: root/crypto/opensslv.h
AgeCommit message (Collapse)AuthorFilesLines
2009-03-31HEAD is now 1.1.0Dr. Stephen Henson1-4/+4
The 1.0.0 branch is now OpenSSL_1_0_0-stable
2009-03-28Nothing to see here... move along....Dr. Stephen Henson1-4/+4
2007-02-17Reorganize the data used for SSL ciphersuite pattern matching.Bodo Möller1-1/+1
This change resolves a number of problems and obviates multiple kludges. A new feature is that you can now say "AES256" or "AES128" (not just "AES", which enables both). In some cases the ciphersuite list generated from a given string is affected by this change. I hope this is just in those cases where the previous behaviour did not make sense.
2005-05-18I just branched 0.9.8, so HEAD needs to be bumped to 0.9.9-dev.Richard Levitte1-3/+3
The 0.9.8 branch is called OpenSSL_0_9_8-stable.
2004-05-17Make reservations for FIPS code in HEAD branch, so that the moment FIPSAndy Polyakov1-0/+4
comes in we have required macros in place.
2002-07-31The version of the shared library should, for now, reflect the versionRichard Levitte1-1/+1
of OpenSSL. Part of PR 181.
2002-04-11Change the date to XX xxx XXXX in development versions.Richard Levitte1-1/+1
2002-02-13Modify the main trunk version to 0.9.8-dev.Richard Levitte1-2/+2
0.9.7 now lives in the branch OpenSSL_0_9_7-stable.
2001-08-10Apply the Tru64 patch from Tim Mooney <mooney@dogbert.cc.ndsu.NoDak.edu>Richard Levitte1-8/+8
His comments are: 1) Changes all references for `True64' to be `Tru64', which is the correct spelling for the OS name. 2) Makes `alpha-cc' be the same as `alpha164-cc', and adds an `alphaold-cc' entry that is the same as the previous `alpha-cc'. The reason is that most people these days are using the newer compiler, so it should be the default. 3) Adds a bit of commentary to Configure, regarding the name changes of the OS over the years, so it's not so confusing to people that haven't been with the OS for a while. 4) Adds an `alpha-cc-rpath' target (which is *not* selected automatically by Configure under any circumstance) that builds an RPATH into the shared libraries. This is explained in the comment in Configure. It's very very useful for people that want it, and people that don't want it just shouldn't choose that target. 5) Adds the `-pthread' flag as the best way to get POSIX thread support from the newer compiler. 6) Updates the Makefile targets, so that when the `alpha164-cc', `alpha-cc', or `alpha-cc-rpath' target is what Configure is set to use, it uses a Makefile target that includes the `-msym' option when building the shared library. This is a performance enhancement. 7) Updates `config' so that if it detects you're running version 4 or 5 of the OS, it automatically selects `alpha-cc', but uses `alphaold-cc' for versions 1-3 of the OS. 8) Updates the comment in opensslv.h, fixing both the OS name typo and adding a reference to IRIX 6.x, since the shared library semantics are virtually identical there.
2001-07-10In version numbers, there is just one "M" nybble.Bodo Möller1-1/+1
2000-10-13Bump the shared library version (should have been done a while ago).Richard Levitte1-1/+1
2000-09-24Update the status and version number to 0.9.7-dev.Richard Levitte1-2/+2
2000-09-24Time to build the release. Bump the version info accordingly.Richard Levitte1-2/+2
2000-09-21Time to build beta 3. Bump the version numbers accordingly.OpenSSL_0_9_6-beta3Richard Levitte1-2/+2
2000-09-17A new beta is being released. Change the version numbersRichard Levitte1-2/+2
accordingly.
2000-09-11Time to release a beta. Change the version numbers and datesRichard Levitte1-3/+3
accordingly.
2000-07-21Redo and enhance the support for building shared libraries. CurrentlyRichard Levitte1-0/+53
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...
2000-04-01Tagging has now been done, update to the next possible version (I keepRichard Levitte1-2/+2
a low profile, so we don't get discontinuity in the numbering...)
2000-04-01Building version 0.9.5aRichard Levitte1-2/+2
2000-03-23Tagging has been done, update to next probable version...Richard Levitte1-2/+2
2000-03-23Time for version 0.9.5a beta2Richard Levitte1-1/+1
I know it's earlier than announced. The high amount of problems in beta1 warants this, however.
2000-03-20Tagging done, we move to the next possible.Richard Levitte1-2/+2
2000-03-20Change the version text, it's time to release the first beta of 0.9.5a.Richard Levitte1-4/+4
2000-03-19Change the notation and coding of the version to be able to containRichard Levitte1-7/+18
both a patch level and a beta status. IMHO, it also makes more sense to have beta status be part of the development status than to have it be an alternate name for patch levels under special conditions.
2000-02-28Tagging has been done, time to switch to 0.9.6-dev.Richard Levitte1-2/+2
2000-02-28Time for a releaseRichard Levitte1-2/+2
2000-02-27For lack of a better name, this is now called 0.9.5beta3-dev until theRichard Levitte1-2/+2
release.
2000-02-27Change version string to reflect the release of beta 2.OpenSSL_0_9_5beta2Richard Levitte1-1/+1
2000-02-25Clarification.Bodo Möller1-1/+1
2000-02-24Version 0.9.5beta2-dev (so that the next snapshot will notBodo Möller1-2/+2
claim to be 0.9.5beta1). (Are the version number examples correct -- the same numerical code for: * 0.9.3beta2-dev 0x00903002 * 0.9.3beta2 0x00903002 ?)
2000-02-240.9.5beta1OpenSSL_0_9_5beta1Richard Levitte1-2/+2
1999-08-09Bump after tarball rolling.Ralf S. Engelschall1-2/+2
Friends, feel free to start again hacking for 0.9.5... ;)
1999-08-09Bump version to 0.9.4OpenSSL_0_9_4Ralf S. Engelschall1-2/+3
1999-05-29And carry on with development...Ben Laurie1-2/+2
1999-05-29Oops!OpenSSL_0_9_3aBen Laurie1-1/+1
1999-05-29Prepare to release 0.9.3aBen Laurie1-3/+3
1999-05-24Move on to 0.9.4.Ben Laurie1-2/+2
1999-05-24Here we go: prepare to roll 0.9.3.OpenSSL_0_9_3Ben Laurie1-2/+2
1999-05-23Move to beta 3.Ben Laurie1-2/+2
1999-05-23Prepare for final(?) beta.OpenSSL_0_9_3beta2Ben Laurie1-1/+1
1999-05-20On seconds thoughts, the version number shoud _never_ decrease.Ben Laurie1-7/+9
1999-05-20Revert.Ben Laurie1-2/+2
1999-05-20Prepare for a beta release.Ben Laurie1-2/+2
1999-05-19Note that the numbering scheme used to be different.Bodo Möller1-0/+1
1999-05-19Switch to new version numbering scheme.Ben Laurie1-2/+11
1999-05-18Protect applications from failing to compile when theyRalf S. Engelschall1-0/+5
try to directly include opensslv.h.
1999-04-01pre-0.9.3 development version.Ulf Möller1-2/+2
1999-03-22Fix security hole.Ben Laurie1-0/+3
generated by cgit v1.1 at 2024-08-11 06:02:00 +0000