openbsd/src/usr.bin/openssl/ts.c, 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 2018-02-07T05:47:55+00:00 Indent labels with a single space so that diff prototypes are more useful. 2018-02-07T05:47:55+00:00 jsing 2018-02-07T05:47:55+00:00 urn:sha1:6d829832b5c1cafa0527a7c2595749b17b0b8efe rearrange pledge promises into the canonical order; easier to eyeball 2017-01-20T08:57:12+00:00 deraadt 2017-01-20T08:57:12+00:00 urn:sha1:ff6fa3ffece7ca61b2a5e2a66b4920c710d4e36b Exit if a pledge call fails in non-interactive mode. 2015-10-17T15:00:11+00:00 doug 2015-10-17T15:00:11+00:00 urn:sha1:db101f70294bca3ebe9eaa1f16aaae8cd872d2e4 ok semarie@ add "tty" for several subcommands of openssl 2015-10-17T07:51:10+00:00 semarie 2015-10-17T07:51:10+00:00 urn:sha1:c93eb1877de5865e80d306506ac0af05c8ac5bde it is needed in order to let libssl UI_* function plays with echo on/off when asking for password on terminal. passwd subcommand needs additionnal "wpath cpath" in order to let it calls fopen("/dev/tty", "w") (O_WRONLY with O_CREAT | O_TRUNC). problem reported by several with and ok doug@ 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. remove vestigial bits of sha-0 and md2 from openssl(1) 2015-09-21T13:13:06+00:00 bcook 2015-09-21T13:13:06+00:00 urn:sha1:ffee1df1db9032d7d2a49bbd051f92e5aad4852c Noted by kinichiro on github. We probably need a better way to indicate the list of message digests that are allowed, as the current ones are nowhere near exhaustive (sigh - guenther@) OK guenther@ jmc@ Temporarily revive MD4 for MS CHAP support. 2015-09-14T01:45:03+00:00 doug 2015-09-14T01:45:03+00:00 urn:sha1:ea990ff7851a189e7a61b56357a6d6e0de88a040 Remove MD4 support from LibreSSL. 2015-09-13T23:36:21+00:00 doug 2015-09-13T23:36:21+00:00 urn:sha1:785c6ad9250acc090d76964e9c21e550856a22f3 MD4 should have been removed a long time ago. Also, RFC 6150 moved it to historic in 2011. Rides the major crank from removing SHA-0. Discussed with many including beck@, millert@, djm@, sthen@ ok jsing@, input + ok bcook@ Nuke SSLEAY_CONF -- a backwards compatibility environment variable that 2015-09-12T19:34:07+00:00 lteo 2015-09-12T19:34:07+00:00 urn:sha1:4ba4f1781a267e49f79cabb109294a61d12f84a0 has been superseded by OPENSSL_CONF and discouraged from use for almost 16 years. "Definately ok" jsing@ "burn it" deraadt@ "Kill it with fire" miod@ "KILL IT WITH FIRE!!! BURN!!!!" beck@ 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@