| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This moves them from .data to .data.rel.ro
ok deraadt@ inoguchi@
|
|
|
|
| |
ok tb@ jsing@
|
|
|
|
|
|
|
|
| |
Much more apt than the current operation names.
Names suggested by jca@ ages ago.
ok jca, jsing
|
|
|
|
|
|
|
|
|
| |
Use more descriptive names, and make it clearer that real and user
timers work on different static storage. The end goal is to be able to
reuse those timer functions, instead of inlining other timer
implementations subject to clock jumps.
Discussed with Scott Cheloha
|
|
|
|
| |
prodding & ok jsing
|
|
|
|
|
| |
where that is long long.
ok beck guenther
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
This pulls out and renames setup_ui/destroy_ui so we have something that
can be replaced as-needed, moving the the console setup code for Windows
to app_win.c in -portable, instead of needing a local patch to enable binary
console mode
ui_read/write are also simplified.
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
ok doug@
|
|
|
|
| |
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@
|