| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
option.
|
|
|
|
|
| |
arbitrary number of arguments. This will allow for more complex option
handling as required by some of the openssl(1) applications.
|
|
|
|
|
| |
that it has consumed. This allows for the handling of multiple unnamed
arguments, including lists of filenames.
|
|
|
|
|
| |
allows for simpler code in the common cases and will allow for further
extension to support the complex cases.
|
| |
|
| |
|
|
|
|
|
| |
values are useable by the function. Also provide an option type that calls
a function without consuming/passing an argument.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
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@
|