| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ok semarie@
|
|
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.
|
|
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@
|
|
that it has consumed. This allows for the handling of multiple unnamed
arguments, including lists of filenames.
|
|
use C99 array initialization syntax for strict C compilers.
from kinichiro, found building with HP/UX compiler
ok deraadt@, guenther@
|
|
ok jsing@
|
|
ERR_load_crypto_strings() - as such, we do not need to call the same
function from most of the applications.
|
|
|
|
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@
|
