| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
ok jmc@
|
|
OpenRCS.
ok xsa, zinovik
|
|
advice and ok martynas@
|
|
should still be better than our current RSA-2048 default.
ok djm@, markus@
|
|
|
|
|
|
|
|
copy it into a newly allocated one (which is even a memory leak).
ok zinovik
|
|
|
|
by and diff from Emanuele Giaquinta.
|
|
some people have it bound to a key.
|
|
|
|
Update our sources appropriately. OK deraadt@ jsg@
|
|
ok gilles@
|
|
|
|
|
|
|
|
Is not used and not useful.
ok xsa, zinovik
|
|
|
|
OpenSSL_add_all_algorithms is the name of the function we have a man page
for, so use that. ok djm
|
|
host/user keys (ECDSA) as specified by RFC5656. ECDH and ECDSA offer
better performance than plain DH and DSA at the same equivalent symmetric
key length, as well as much shorter keys.
Only the mandatory sections of RFC5656 are implemented, specifically the
three REQUIRED curves nistp256, nistp384 and nistp521 and only ECDH and
ECDSA. Point compression (optional in RFC5656 is NOT implemented).
Certificate host and user keys using the new ECDSA key types are supported.
Note that this code has not been tested for interoperability and may be
subject to change.
feedback and ok markus@
|
|
string extracted from the buffer contains no embedded \0 characters*
This prevents random (possibly malicious) crap from being appended to
strings where it would not be noticed if the string is used with
a string(3) function.
Use the new API in a few sensitive places.
* actually, we allow a single one at the end of the string for now because
we don't know how many deployed implementations get this wrong, but don't
count on this to remain indefinitely.
|
|
sys/types.h is the file you want to include.
|
|
|
|
ok millert guenther
|
|
bufferevent) before freeing the bufferevent.
|
|
reported by gcc.
ok jasper@
|
|
idiotically accepts more then two hex digits following the \x, even
on platforms where a char has 8 bits. It is therefore dangerous to have
an almost-bit-not-quite compatible format in vis(3).
The VIS_ALL (encode all characters) option introduced in the same commit
remains.
|
|
.tiprc reported by nick@.
|
|
when setting up the client.
|
|
|
|
size as well. Stops the client fatal()ing on exit.
|
|
hex encoding. feedback jmc@ ok millert@
|
|
As Kristaps found out, i was wrong: .Bl -column phrases do not ignore
spacing rules for trailing punctuation in general. In particular,
- the rightmost column of a column list is unaffected
- columns terminated by the .Ta macro instead of a tab are unaffected
- columns ending in a blank are unaffected
Spacing rules for trailing punctuation are only ignored when the tab
follows the punctuation immediately, without a blank in between,
because then the combination of punctuation and tab is treated by roff
as a word, and the punctuation is not recognized as isolated.
The reason this doesn't work in mandoc is that in the special case
of .Bl -column (not in general!), mandoc treats tabs as word delimiters.
We either need to solve this differently, or call it a bug in roff.
|
|
making the code simpler and easier to understand.
No functional change.
|
|
to the start of the next column correctly.
Fixing a problem found by jmc@ in sysctl(3), reminded by kettenis@.
|
|
and render it just like normal text.
Minimal fix of a formatting bug in operator(7) reported by ray@.
|
|
skip output functions, but not *_endparse;
problem reported by kristaps@
|
|
fix NULL vs 0, etc. No behaviour change.
|
|
We now have sufficient practical experience to know what we want,
so this is intended to be final:
- provide -Wlevel (warning, error or fatal) to select what you care about
- provide -Wstop to stop after parsing a file with warnings you care about
- provide consistent exit status codes for those warnings you care about
- fully document what warnings, errors and fatal errors mean
- remove all other cruft from the user interface, less is more:
- remove all -f knobs along with the whole -f option
- remove the old -Werror because calling warnings "fatal" is silly
- always finish parsing each file, unless fatal errors prevent that
This commit also includes a couple of related simplifications behind
the scenes regarding error handling.
Feedback and OK kristaps@; Joerg Sonnenberger (NetBSD) and
Sascha Wildner (DragonFly BSD) agree with the general direction.
|
|
directly instead - calling libevent functions after fork() w/o
event_reinit() is a bad idea, even if in this case it was harmless.
|
|
already dup()d again later. Fixes a leak seen by espie@.
|
|
used as filename
|
|
as suggested by Thomas de Grivel <billitch at gmail dot com> on tech@.
While here, remove the SEE ALSO entries (but not the cross references
at the appropriate places!) to fnmatch(3), re_format(7), and pr(1).
Their relevance is restricted to one single option each, the latter
is mostly obsolete nowadays anyway, and the number of SEE ALSO entries
is so large that SEE ALSO is starting to look confusing.
"yes" jmc@
|
|
It is always defined in the preamble using .ds when used in manuals.
Since we now support .ds, it is no longer necessary to provide it.
Triggered by a bug report from Thomas Jeunet, patch by kristaps@.
|
|
just in the same way as \s (font size) escapes, and handle \s escapes
not having an explicit plus or minus sign.
This fixes the very ugly rendering of "C++" in gcc(1).
Reported by Thomas Jeunet, fixed by kristaps@.
|
|
Issue reported by Aldis Berzoja, fix by kristaps@.
|
|
from kristaps@.
|
