summaryrefslogtreecommitdiff
path: root/src/usr.bin/openssl/rand.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* sprinkle some void between () in function definitionstb2023-07-231-2/+2
|
* Rename struct ${app}_config to plain cfgtb2023-03-061-12/+12
| | | | | | | | | All the structs are static and we need to reach into them many times. Having a shorter name is more concise and results in less visual clutter. It also avoids many overlong lines and we will be able to get rid of some unfortunate line wrapping down the road. Discussed with jsing
* openssl: make all config structs statictb2023-03-051-2/+2
| | | | | These are per-app, so per-file. Most of them already are static, adjust the rest of them.
* Remove the legacy interactive mode from openssl(1).joshua2022-11-111-6/+4
| | | | | | | | This removes the legacy interactive mode from openssl(1) since it is rarely used, complicates the code, and has also been removed from OpenSSL in version 3.x.x. ok tb@ jsing@
* Mark the initialized struct options arrays as both static and const.guenther2019-07-141-2/+2
| | | | | | This moves them from .data to .data.rel.ro ok deraadt@ inoguchi@
* Indent labels with a single space so that diff prototypes are more useful.jsing2018-02-071-2/+2
|
* Remove guards around *_free() calls since these functions handle NULL.jsing2018-02-071-3/+2
|
* rearrange pledge promises into the canonical order; easier to eyeballderaadt2017-01-201-2/+2
|
* Exit if a pledge call fails in non-interactive mode.doug2015-10-171-2/+4
| | | | ok semarie@
* Initial support for pledges in openssl(1) commands.doug2015-10-101-1/+6
| | | | | | | | | | | | | | | | openssl(1) has two mechanisms for operating: either a single execution of one command (looking at argv[0] or argv[1]) or as an interactive session than may execute any number of commands. We already have a top level pledge that should cover all commands and that's what interactive mode must continue using. However, we can tighten up the pledges when only executing one command. This is an initial stab at support and may contain regressions. Most commands only need "stdio rpath wpath cpath". The pledges could be further restricted by evaluating the situation after parsing options. deraadt@ and beck@ are roughly fine with this approach.
* Remove engine command and parameters from openssl(1).bcook2015-09-111-16/+2
| | | | | | | We do not have any builtin or dynamic engines, meaning openssl(1) has no way to use the engine command or parameters at all. ok jsing@
* Remove all duplicate prototypes for *_main functions (these are alreadyjsing2015-08-221-3/+1
| | | | | | | | | provided by progs.h). Also, move the FUNCTION type (and flags) into openssl.c since that is the only place of use. Lastly, remove pointless 'extern' from the prototypes and use char **argv instead of char *argv[] (the former is used elsewhere). ok deraadt@ doug@
* Provide a mechanism for option parsing to return the number of argumentsjsing2014-12-281-2/+2
| | | | | that it has consumed. This allows for the handling of multiple unnamed arguments, including lists of filenames.
* Use arc4random_buf() instead of RAND(_pseudo)?_bytes().jsing2014-10-221-5/+2
| | | | ok bcook@
* prefer C99 array initialization syntax.bcook2014-10-131-2/+2
| | | | | | | | use C99 array initialization syntax for strict C compilers. from kinichiro, found building with HP/UX compiler ok deraadt@, guenther@
* Reset the config struct before calling options_parse(), otherwise configjsing2014-08-271-1/+3
| | | | options from the previous run stick in interactive mode.
* Implement table-driven option parsing that allows an application tojsing2014-08-271-74/+75
| | | | | | | | | | | | | | | | | specify what its valid options are and where it wants them to be stored. This also allows for usage to be generated, almost for free, ensuring that the options and usage are automatically kept in sync. This will allow for a single option parsing implementation, rather than the current one-hand-rolled-option-parsing-and-random-usage-implementation per application. As a starting point, port the openssl(1) rand application to the new option parsing and usage (along with associated code clean up). With input from doug@. ok bcook@ doug@
* Move openssl(1) from /usr/sbin/openssl to /usr/bin/openssl, since it is notjsing2014-08-261-0/+194
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@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-19 23:42:31 +0000