| Age | Commit message (Collapse) | Author |
|---|
|
an untraced process but finds it blocking or ignoring it, just kill
the process instead of looping. It's undefined behavor in POSIX but
quite annoying when encountered in practice.
improvements from kettenis@
ok matthew@
|
|
|
|
ok deraadt@
|
|
to avoid duplication. Also use fewer magic numbers.
ok miod@
|
|
From OpenSSL.
ok miod@
|
|
ok miod@
|
|
with "mandoc: " or "makewhatis: ", respectively,
similar to what we already do for other messages.
|
|
available via boringssl.
ok deraadt@
|
|
correct record is already known, so avoid reassignment.
|
|
|
|
|
|
|
|
|
|
|
|
OK from miod@
|
|
fix _dl_strdup to return NULL instead of crash; ok deraadt@
|
|
From: "Craig R. Skinner"
|
|
From Egbert Eich
9e68a1156da093385f057b9e4576652203f1248e in ubuntu 3.8
7f1950fbb989e8fc5463b307e062b4529d51c862 in mainline linux
|
|
From Alex Deucher
eed35bff1fe05f3a32989ace86107a1402f18537 in ubuntu 3.8
8c79bae6a30f606b7a4e17c994bc5f72f8fdaf11 in mainline linux
|
|
From Quentin Casasnovas
2b9149f17e7135c31c9df1c80ab6d912c4265126 in ubuntu 3.8
74073c9dd29905645feb6dee03c144657a9844cd in mainline linux
|
|
Modern compiler toolchains are capable of optimizing even across
translation unit boundaries, so simply moving the memory clearing into
a separate function is not guaranteed to clear memory.
To avoid this, we take advantage of ELF weak symbol semantics, and
insert a call to an empty, weakly named function. The semantics of
calling this function aren't determinable until load time, so the
compiler and linker need to keep the memset() call.
There are still ways a toolchain might defeat this trick (e.g.,
optimistically expecting the weak symbol to not be overloaded, and
only calling memset() if it is; promoting weak symbols to strong
symbols at link-time when emitting a static binary because they won't
be interposed; implementing load-time optimizations). But at least
for the foreseeable future, these seem unlikely.
ok deraadt
|
|
|
|
when they are meaningful, to avoid confusing stuff like this:
$ mandoc /dev/null
mandoc: /dev/null:0:1: FATAL: not a manual
Instead, just say:
mandoc: /dev/null: FATAL: not a manual
Another example this applies to is documents having a prologue,
but lacking a body. Do not throw a FATAL error for these; instead,
issue a warning and show the empty document, in the man(7) case with
the same amount of blank lines as groff does. Also downgrade mdoc(7)
documents having content before the first .Sh from FATAL to WARNING.
|
|
change the behaviour of the library in such a complicated fashion.
ok miod
|
|
setuid applications from being fooled.
ok miod
|
|
/dev/urandom. Does well in the fallback case. Get it in tree so
it can be worked on.
ok otto@ deraadt@
|
|
|
|
Even though messages are not going to be as stable as formatted output,
that is, even though the *.out_lint files are expected to change now and then,
from now on, i want to be able to catch unintended changes in messages.
|
|
So far, this covers all WARNINGs related to the prologue.
1) hierarchical naming of MANDOCERR_* constants
2) mention the macro name in messages where that adds clarity
3) add one missing MANDOCERR_DATE_MISSING msg
4) fix the wording of one message related to the man(7) prologue
Started on the plane back from Ottawa.
|
|
just like almost all other utility programs do.
Suggested by nick@ who wondered where messages came from
when calling mandoc(1) from inside a Perl script.
ok jmc@ nick@
|
|
have been used under DJGPP in the previous century (if at all).
|
|
ok syl@
|
|
|
|
to faff around with huge numbers to get everything.
|
|
noticed and fix by Fedor Indutny of Joyent
( https://github.com/joyent/node/issues/7704 )
|
|
( https://github.com/joyent/node/issues/7704 ), about to be fixed in
libcrypto.
|
|
it getting siblings.
|
|
this breaks when compiling a kernel with DEBUG defined for additional
printfs elsewhere. Instead of renaming the macro, undefine DEBUG
before the new definition to minimise the diff the linux.
|
|
infrastructure.
The following tests have not been imported, for their code lacks a licence:
asn1, rsa, sha256, sha512, wp.
|
|
|
|
checksum, make tcpdump (with the -v flag) show the actual bad checksum
within the IP/protocol header itself and what the good checksum should
be, e.g. "[bad tcp cksum abcd! -> d1e6]"
This change applies to IP, TCP (over IPv4 and IPv6), UDP (over IPv4 and
IPv6), ICMP, and ICMPv6. This commit also fixes several inconsistencies
in the way bad checksums were displayed for these protocols.
Tested on amd64, i386, and macppc.
ok henning@
|
|
upcoming commit which will fix and improve the display of bad checksums
for the major protocols.
ok henning@
|
|
1) Do not error out when getcwd(3) fails, only fail when inaccessibility
of the cwd prevents processing of relative paths given on the command line.
2) Do not uselessly call set_basedir() twice in a row.
While fts_read(3) in treescan() does cause the cwd to jump around,
fts_close(3) is always called at the end, putting us back
where we came from. The -d/-u fallback code already relied on this.
3) Fix the man-root-dir indicator in say().
|
|
Allow other non-zero return values in case we change our mind to
return an ssize_t byte count instead of simple success/fail.
ok deraadt, djm
|
|
libc interfaces over libcrypto interfaces. for now we also prefer
timingsafe_memcmp over timingsafe_bcmp, even when the latter is acceptable.
ok beck deraadt matthew miod
|
|
|
|
add missing unlock in one case. ok lteo miod
|
|
|
|
|
|
ok miod@, dlg@
|
