openbsd/src/usr.bin/openssl/apps.h, branch OPENBSD_6_8_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE 2020-09-09T12:47:46+00:00 Add option type OPTION_UL_VALUE_OR 2020-09-09T12:47:46+00:00 inoguchi 2020-09-09T12:47:46+00:00 urn:sha1:3cfba77da9bef4c2ccb36f7eb800f040c0d30b0f ok tb@ Mark the initialized struct options arrays as both static and const. 2019-07-14T03:30:46+00:00 guenther 2019-07-14T03:30:46+00:00 urn:sha1:ce9daaa0080f6ec467441aa485eb3f11ad6fb74a This moves them from .data to .data.rel.ro ok deraadt@ inoguchi@ Summarize the 4 same name functions and move it to apps.c 2019-02-09T06:27:37+00:00 inoguchi 2019-02-09T06:27:37+00:00 urn:sha1:fa558a77721eb21feb6a123f6212126f9de94b24 ok tb@ jsing@ openssl app timers: TM_START -> TM_RESET, TM_STOP -> TM_GET 2018-07-13T18:36:56+00:00 cheloha 2018-07-13T18:36:56+00:00 urn:sha1:ac5e763160d1b0cf0a2c6f4caf5442f2cb1675cc Much more apt than the current operation names. Names suggested by jca@ ages ago. ok jca, jsing Seperate real and user timer interfaces 2017-12-05T15:02:06+00:00 jca 2017-12-05T15:02:06+00:00 urn:sha1:18630b1588538df9b732e385e1ca2642df0abc87 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 Add OPTION_ARG_TIME for parsing a (64 bit if needed) time_t 2016-08-30T14:34:59+00:00 deraadt 2016-08-30T14:34:59+00:00 urn:sha1:eef10b416862b4920a59237babe254fb5ab98c68 prodding & ok jsing Fix 32-bit time handling, using time_t and make it work on systems 2016-08-30T11:30:14+00:00 deraadt 2016-08-30T11:30:14+00:00 urn:sha1:7bd8de9813fc866790eb5608a43725a52ce21d14 where that is long long. ok beck guenther Initial support for pledges in openssl(1) commands. 2015-10-10T22:28:51+00:00 doug 2015-10-10T22:28:51+00:00 urn:sha1:503cf2bd70538bb9cc734a5fd58230b90be4d1d8 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. Factor out setup_up / destroy_ui functions. 2015-09-13T12:41:01+00:00 bcook 2015-09-13T12:41:01+00:00 urn:sha1:22c85357bfe5c53ac5831efbd4810877f6795bd9 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. Remove engine command and parameters from openssl(1). 2015-09-11T14:30:23+00:00 bcook 2015-09-11T14:30:23+00:00 urn:sha1:e8587be16102f0811af023382ffaeb2002feec78 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@