openbsd/src/lib/libcrypto/man, branch OPENBSD_6_0_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_0_BASE 2016-07-05T02:54:35+00:00 On systems where we do not have BN_ULLONG defined (most 64-bit systems), 2016-07-05T02:54:35+00:00 bcook 2016-07-05T02:54:35+00:00 urn:sha1:29ecf1f5b4cb5a580dcac440216b7127a56e3f84 BN_mod_word() can return incorrect results if the supplied modulus is too big, so we need to fall back to BN_div_word. Now that BN_mod_word may fail, handle errors properly update the man page. Thanks to Brian Smith for pointing out these fixes from BoringSSL: https://boringssl.googlesource.com/boringssl/+/67cb49d045f04973ddba0f92fe8a8ad483c7da89 https://boringssl.googlesource.com/boringssl/+/44bedc348d9491e63c7ed1438db100a4b8a830be ok beck@ for some time now mandoc has not required MLINKS to function 2016-03-30T06:38:43+00:00 jmc 2016-03-30T06:38:43+00:00 urn:sha1:2cadae282cf8545afbe05fc59db59e3fd30c67e0 correctly - logically complete that now by removing MLINKS from base; authors need only to ensure there is an entry in NAME for any function/ util being added. MLINKS will still work, and remain for perl to ease upgrades; ok nicm (curses) bcook (ssl) ok schwarze, who provided a lot of feedback and assistance ok tb natano jung fix the last bunch of NAME sections that were overlooked earlier 2016-03-26T14:36:37+00:00 schwarze 2016-03-26T14:36:37+00:00 urn:sha1:0073f6ca24b1278000926485be175f8f706a8867 such that the MLINKS removal can be committed after this; OK jmc@ Remove sentences in RETURN VALUES sections saying that functions with 2016-03-12T21:31:22+00:00 mmcc 2016-03-12T21:31:22+00:00 urn:sha1:d7e23979f786be3c146be16ec4363c6da83c906e void return types 'return no value'. This is obvious and therefore unneccessary to mention. We spare rewind(3)'s sentence because espie@ pointed out that it's a warning - the function masks a potential error. This commit also adds a sentence to X509_free clarifying that it's NULL-safe. This bit was discussed with doug@. ok martijn@, sentiment supported by schwarze@ Correct file name, no text change (no history yet, but sorry for the churn). 2015-11-24T19:36:35+00:00 schwarze 2015-11-24T19:36:35+00:00 urn:sha1:0dbd386e3a1720959cdaa0731b8feb9c2c5b62dd Issue noticed by jmc@, OK jmc@. Partial revert of revision 1.26: 2015-11-21T14:20:07+00:00 schwarze 2015-11-21T14:20:07+00:00 urn:sha1:730c3717ada7eccd975d1429ac21188b1731a372 Do *not* install the CMS_* manuals for now given that the code is currently disabled. Cluestick applied by jsing@. ui_new -> UI_new; 2015-11-15T22:06:51+00:00 jmc 2015-11-15T22:06:51+00:00 urn:sha1:42c67978b7a48cd55b94760ebd970a53df69566d add mul and mul_add to NAME; 2015-11-12T09:51:55+00:00 jmc 2015-11-12T09:51:55+00:00 urn:sha1:162c0cc5a30a453572ea437399279a4e5a0276e0 update cross references after deleting the imaginary MLINKS 2015-11-12T01:07:50+00:00 schwarze 2015-11-12T01:07:50+00:00 urn:sha1:cd9cf4a16de9a17957b1a6215b9949d460d1efc9 bn_internal(3) and lhash(3) Convert the handful of manuals that had imaginary names, 2015-11-12T00:55:49+00:00 schwarze 2015-11-12T00:55:49+00:00 urn:sha1:f6fb651984e778ed504d05ec0e403437b6f5812c give them names that really exist. This also helps jmc@'s ongoing work on improving NAME sections.