Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | tweak column widths of a .Bl -column table | 2021-03-31 | 1 | -3/+4 | |
| | | | | | and avoid an over-long source line while here; OK martijn@ jmc@ | ||||
* | change the barrier so that fd's are always passed and received with | 2021-03-31 | 1 | -8/+10 | |
| | | | | | | the first byte of the imsg they belong to. idea, tweaks and ok claudio@ | ||||
* | fix previous | 2021-03-12 | 1 | -2/+2 | |
| | |||||
* | spelling | 2021-03-12 | 3 | -9/+9 | |
| | |||||
* | Stop abusing display blocks under the authors section in order to | 2021-03-05 | 1 | -4/+4 | |
| | | | | | | | | respect literal line breaks. This has the unwanted side effect of rendering the authors section using a monospace font over at man.openbsd.org. Instead use br macros to force line breaks. With help from and ok jmc@ | ||||
* | s/byte/character | 2021-03-03 | 1 | -8/+8 | |
| | | | | | Discussed with claudio@ Feedback jmc@ | ||||
* | Make the ober_get_* set of function to accept a NULL-pointer. | 2021-02-22 | 2 | -16/+55 | |
| | | | | | | | | This allows us to do ber-type checking inside ober_scanf_elements, which will allow for stricter ASN.1 parsing in the future. Manpage feedback and OK claudio@, jmc@ OK claudio@ | ||||
* | Add '$' to ober_scanf_elements(). | 2021-01-28 | 2 | -4/+13 | |
| | | | | | | | | This allows us to enforce end of sequence/set without having to manually check be_next for NULL. No lib bump needed according to millert@ OK millert@ rob@ | ||||
* | Gracefully handle any erroneous closing bracket/brace trailers in | 2021-01-22 | 1 | -2/+2 | |
| | | | | | | ober_scanf_elements(). OK martijn@ | ||||
* | Valid integer and enumerated types always have non-zero length. Perform | 2021-01-22 | 1 | -1/+5 | |
| | | | | | | | check to ensure we avoid a possible (undefined) negative shift. Found with clang static analyzer. Tweaked and OK martijn@ | ||||
* | Make imsg.h a bit more self-contained by prototyping struct iovec. | 2021-01-13 | 1 | -1/+2 | |
| | | | | OK martijn@ mvs@ deraadt@ | ||||
* | typo fix from aisha tammy; ok nicm | 2020-12-15 | 1 | -3/+3 | |
| | |||||
* | double word fixes; from varik valefor | 2020-10-16 | 1 | -3/+3 | |
| | |||||
* | make fixed-sized fixed-value mib[] arrays be const | 2020-10-12 | 3 | -12/+10 | |
| | | | | ok guenther tb millert | ||||
* | Create ERRORS section for ober_read_elements. | 2020-09-04 | 1 | -6/+29 | |
| | | | | | Tweaks and OK tb@ OK jmc@ | ||||
* | Missed one case of errno not being set in previous. | 2020-09-03 | 1 | -2/+4 | |
| | | | | double check and OK tb@ | ||||
* | Make sure ober_read_elements sets errno on every case where NULL is | 2020-09-03 | 1 | -4/+10 | |
| | | | | | | returned. OK deraadt@ tb@ | ||||
* | Squelch warning by using idiom from libc bcrypt(3) | 2020-08-02 | 1 | -2/+2 | |
| | | | | | | | | | Clang 10 warns about the expression sizeof(cdata) / sizeof(uint64_t) as cdata is an array of uint32_t and it expects that the intent of this is to compute the number of array elements. Use BCRYPT_WORDS / 2 instead. Same diff as millert's commit sys/lib/libsa/bcrypt_pbkdf.c -r1.2, which was ok kettenis. deraadt confirms that this satisfies clang 10. | ||||
* | Increase BER_MAX_OID_LEN from 32 to 64. Not every snmp OID found in the | 2019-12-31 | 3 | -6/+6 | |
| | | | | | | wild fits inside 32 elements, like UsmUserEntry objects. OK rob@, claudio@ | ||||
* | zero tmpout too. reminded by related diff from tim | 2019-11-21 | 1 | -1/+2 | |
| | |||||
* | overwrite the key in failure modes in case the caller doesn't check. | 2019-11-21 | 2 | -7/+17 | |
| | | | | ok deraadt | ||||
* | Adjust whitespace, so Ta macros are aligned vertically as already done in | 2019-10-25 | 1 | -7/+7 | |
| | | | | ober_add_string.3 and as it was before the ber -> ober rename. | ||||
* | The ber_* namespace is used by liblber since time immemorial, | 2019-10-24 | 10 | -438/+439 | |
| | | | | | | | | | | | | so move our BER API to the unused ober_* prefix to avoid some breakage in ports. Problem diagnosed by jmatthew with ber_free() in samba, but there are many others as pointed out by sthen. tests & ok rob ok sthen (who had an almost identical diff for libutil) "go head hit it" deraadt | ||||
* | uucplock(3) is incorrectly named in some places, it is actually uu_lock(3) | 2019-08-30 | 3 | -6/+6 | |
| | | | | (more unclear is if anything in ports uses this, as our base no longer does) | ||||
* | Revert previous. There were some users of the quirky behaviour that were | 2019-08-15 | 1 | -2/+2 | |
| | | | | missed during code scan. | ||||
* | Fix argument list for ber_set_writecallback | 2019-08-14 | 1 | -3/+5 | |
| | | | | OK claudio@ | ||||
* | wonky comma; | 2019-08-14 | 1 | -3/+3 | |
| | |||||
* | Document that ber_scanf_elements' 'p' and 't' attribute don't eat the | 2019-08-14 | 1 | -2/+7 | |
| | | | | | | | current ber element. OK claudio@ Seems sensible to deraadt@ | ||||
* | Make ber_scanf_elements's 'e' attribute eat the element. | 2019-08-14 | 1 | -2/+2 | |
| | | | | | | | | Right now all consumers use 'e' at the end of the list, so no regressions should be introduced. OK claudio@ Seems sensible to deraadt@ | ||||
* | Make sure that ber in ber_scanf_elements is not NULL before parsing format | 2019-08-14 | 1 | -3/+3 | |
| | | | | | | | | | where ber is utilized. This also allows us to remove the ber->be_next check, which can cause weird behaviour, because a NULL be_next would result in parsing the last element twice. OK claudio@ on previous version OK rob@ | ||||
* | Don't use a 0 element to determine the end of an OID when comparing two | 2019-08-05 | 1 | -17/+17 | |
| | | | | | | OIDS. This can result in false equality matches. OK claudio@ | ||||
* | There's no reason why the first digit of an OID can't be 0. | 2019-08-05 | 1 | -4/+1 | |
| | | | | | OK claudio@ "Good find" deraadt@ | ||||
* | snprintf/vsnprintf return < 0 on error, rather than -1. | 2019-07-03 | 1 | -7/+9 | |
| | |||||
* | Actually, the C standard only guarantees that atexit(3) returns non-zero | 2019-06-28 | 1 | -2/+2 | |
| | | | | | on error, so tweak previous to test "atexit(...) != 0" for portability. "OK ok ok sorry backwards" deraadt@ | ||||
* | When system calls indicate an error they return -1, not some arbitrary | 2019-06-28 | 8 | -24/+24 | |
| | | | | | | value < 0. errno is only updated in this case. Change all (most?) callers of syscalls to follow this better, and let's see if this strictness helps us in the future. | ||||
* | atexit() returns -1 on failure | 2019-06-28 | 1 | -2/+2 | |
| | |||||
* | Limit maximum number of length octets to platform independent sizeof(int32_t). | 2019-06-01 | 1 | -2/+5 | |
| | | | | | | Problem noticed by bluhm@. Discussed on hackers. ok claudio@ | ||||
* | whitespace | 2019-05-21 | 1 | -2/+2 | |
| | |||||
* | Cleanup some residual markup from the ber.3 days. | 2019-05-21 | 5 | -29/+17 | |
| | | | | ok jmc@, schwarze@ | ||||
* | add various missing information | 2019-05-17 | 1 | -29/+75 | |
| | | | | | and remove the lie that these functions would set errno; tweaks and OK jmc@; OK rob@ on the previous version | ||||
* | Add XXX to a comment. | 2019-05-16 | 1 | -2/+2 | |
| | |||||
* | Correct errno markup. Noticed by schwarze. | 2019-05-16 | 2 | -6/+6 | |
| | | | | Discussed with schwarze and jmc. ok schwarze | ||||
* | sort SEE ALSO; | 2019-05-15 | 2 | -8/+8 | |
| | |||||
* | add substantial amounts of missing information; | 2019-05-15 | 1 | -24/+96 | |
| | | | | OK rob@ | ||||
* | Consistently make errno a .Vt | 2019-05-15 | 2 | -6/+8 | |
| | |||||
* | delete some duplicate words | 2019-05-15 | 1 | -4/+2 | |
| | |||||
* | Split ber.3 into logical parts. Further tweaking will be done in tree. | 2019-05-15 | 7 | -456/+769 | |
| | | | | Discussed with and ok jmc@, schwarze@, claudio@ | ||||
* | Enable support for the writting of BITSTRING by treating it as an OCTETSTRING. | 2019-05-12 | 1 | -2/+1 | |
| | | | | ok claudio@ | ||||
* | Enforce smallest number of contents octets for int (and enum). | 2019-05-12 | 1 | -2/+9 | |
| | | | | ok claudio@ | ||||
* | Mention #include of <sys/types.h> in synopsis. | 2019-05-12 | 1 | -2/+3 | |
| | | | | Discussed with claudio@ and tedu@. |