summaryrefslogtreecommitdiffstats
path: root/lib/libssl/src/apps/pkeyutl.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Move openssl(1) from /usr/sbin/openssl to /usr/bin/openssl, since it is notjsing2014-08-261-503/+0
| | | | | | | | a system/superuser binary. At the same time, move the source code from its current lib/libssl/src/apps location to a more appropriate home under usr.bin/openssl. ok deraadt@ miod@
* whitespacederaadt2014-07-141-5/+5
|
* openssl(1) is only built as a single monolithic binary, so just calljsing2014-07-121-4/+1
| | | | | | load_config() once when we start. ok miod@
* tags as requested by miod and teduderaadt2014-06-121-0/+1
|
* if (x) free(x) -> free(x); semantic patch generated with coccinelle, carefullymiod2014-05-221-2/+1
| | | | eyeballed before applying. Contributed by Cyril Roelandt on tech@
* It is perfectly valid to call free(NULL), so stop checking for non-NULLjsing2014-05-191-6/+4
| | | | before calling free - of some course parts of the code already did this.
* Group and sort includes.jsing2014-05-181-4/+3
| | | | | | | | Currently "apps.h" needs to be included before any of the openssl headers and there are several cases where the code depends on headers that are included by something included by apps.h... More untangling saved for later on.
* bio_err is initialised in main, hence there is no need to initialise itjsing2014-05-181-3/+1
| | | | | | | | | | | | in each application (since there is no longer a non-monolithic mode). In typical OpenSSL fashion, the code is inconsistent and there are multiple ways that bio_err was initialised - none of them actually checked to see if the initialisation actually succeeded. Additionally, it is worth noting that in at least two cases bio_err was also being used before it would have been initialised. ok miod@
* $HOME/.rnd will never be a good source of entropy. ok becktedu2014-04-181-2/+0
|
* whitespace normalizationtedu2014-04-181-6/+3
|
* Remove MAIN and PROG defines now that we do not compile non-monolithic.jsing2014-04-181-4/+2
| | | | ok tedu@
* KaboomNFtedu2014-04-181-232/+186
|
* Change library to use intrinsic memory allocation functions instead ofbeck2014-04-171-5/+5
| | | | | | | | OPENSSL_foo wrappers. This changes: OPENSSL_malloc->malloc OPENSSL_free->free OPENSSL_relloc->realloc OPENSSL_freeFunc->free
* spray the apps directory with anti-VMS napalm.tedu2014-04-161-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | so that its lovecraftian horror is not forever lost, i reproduce below a comment from the deleted code. /* 2011-03-22 SMS. * If we have 32-bit pointers everywhere, then we're safe, and * we bypass this mess, as on non-VMS systems. (See ARGV, * above.) * Problem 1: Compaq/HP C before V7.3 always used 32-bit * pointers for argv[]. * Fix 1: For a 32-bit argv[], when we're using 64-bit pointers * everywhere else, we always allocate and use a 64-bit * duplicate of argv[]. * Problem 2: Compaq/HP C V7.3 (Alpha, IA64) before ECO1 failed * to NULL-terminate a 64-bit argv[]. (As this was written, the * compiler ECO was available only on IA64.) * Fix 2: Unless advised not to (VMS_TRUST_ARGV), we test a * 64-bit argv[argc] for NULL, and, if necessary, use a * (properly) NULL-terminated (64-bit) duplicate of argv[]. * The same code is used in either case to duplicate argv[]. * Some of these decisions could be handled in preprocessing, * but the code tends to get even uglier, and the penalty for * deciding at compile- or run-time is tiny. */
* import OpenSSL 1.0.0edjm2011-11-031-6/+6
|
* import OpenSSL-1.0.0adjm2010-10-011-1/+1
|
* import of OpenSSL 0.9.8kdjm2009-04-061-0/+570
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.