| Age | Commit message (Collapse) | Author |
|---|
|
from Nir Lichtman
ok pascal sthen
(they okayed the ports version which I take to be an agreement with this).
|
|
|
|
|
|
|
|
doesn't complain when it's implicitly converted to plain char in an
assignment, and to make sure it's not negative when used as an array index.
ok miod@
|
|
to a function pointer definition.
ok miod@
|
|
ok miod@
|
|
just delete the bogus declarations. Also, getopt() is in <unistd.h>
so pull that in during the remapping of it.
ok miod@
|
|
bad buffer size.
ok miod@
|
|
A bit more grumpy about bad texinfo, though.
|
|
|
|
|
|
This causes the caller to cleans the return address off the stack after
a callq completes. The option is best used in low-level libraries (such as
libc), because libc contains low-level system call stubs. The option
reduces hints (found on the stale parts of the stack) about libc.so's mapping
location, and together with random-relinking, relro got/pic, and xonly
makes some exploit methods more difficult.
ok mortimer, mlarkin, much discussion with kettenis, in snaps for 2 weeks.
|
|
failure when using make -j; this used to be hidden because of the objective-C
generated files, which are no longer built. No change for regular make.
|
|
When calling POSIX::setlocale() with unknown locale category, Perl
could crash due to NULL dereference.
found by sthen@ in smokeping build; OK afresh1@
|
|
ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@
|
|
ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@
|
|
ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@
|
|
ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@
|
|
OK sthen@
|
|
Timing is good deraadt@, OK sthen@
|
|
looking good sthen@, Great! bluhm@
|
|
|
|
|
|
|
|
Ever since the prehistoric zlib was removed last fall, the configure script
would complain because of a missing file:
sed: 0: /usr/src/gnu/usr.bin/cvs/zlib/Makefile.in: No such file or directory
noticed by deraadt
ok bluhm
|
|
.openbsd.syscalls section with the PT_OPENBSD_SYSCALLS phdr, even though is
does not have the ALLOC flag; otherwise the phdr gets rewritten with a size
of zero, which prevents the binary from working.
ok kettenis@
|
|
|
|
(libobjc) had been removed from the build years ago, there is no need to
keep the compiler.
ok beck@ joshua@
|
|
|
|
|
|
first six entries are in the same order as syscall arguments, such
that syscall() can just use the trapframe as the argument vector
for mi_syscall() and not need to reorder into another buffer on the
stack. This doesn't affect coredump layout or ptrace(2), but does
affect kernel crash dumps.
Possibility noted during miod@'s cleanup of the MD syscall()
implementations
ok mlarkin@ kurt@
|
|
endbr{64,32}
"sure" dv@ deraadt@
|
|
Repairs ld.bfd operations on i386: since the switch to llvm-16 clang
emits such relocations (eg one is present in /usr/lib/crtbegin.o).
This unbreaks the build of ports/lang/fpc.
Help and tests from tb@, ok tb@ kettenis@
|
|
No changes to perl, as those were already committed for the earlier errata.
This just brings documentation and such in line with upstream.
ok bluhm@
|
|
of which there is only one -- instbin, on the install media. But
that is incompatible with the 32-bit offsets in openbsd.syscalls.
Move the start of openbsd nopie binaries much lower.
ok kettenis
|
|
This will be used soon to pin system calls to designated call sites.
ok deraadt@
|
|
From upstream commit:
From 7047915eef37fccd93e7cd985c29fe6be54650b6 Mon Sep 17 00:00:00 2001
From: Karl Williamson <khw@cpan.org>
Date: Sat, 9 Sep 2023 11:59:09 -0600
Subject: [PATCH] Fix read/write past buffer end: perl-security#140
A package name may be specified in a \p{...} regular expression
construct. If unspecified, "utf8::" is assumed, which is the package
all official Unicode properties are in. By specifying a different
package, one can create a user-defined property with the same
unqualified name as a Unicode one. Such a property is defined by a sub
whose name begins with "Is" or "In", and if the sub wishes to refer to
an official Unicode property, it must explicitly specify the "utf8::".
S_parse_uniprop_string() is used to parse the interior of both \p{} and
the user-defined sub lines.
In S_parse_uniprop_string(), it parses the input "name" parameter,
creating a modified copy, "lookup_name", malloc'ed with the same size as
"name". The modifications are essentially to create a canonicalized
version of the input, with such things as extraneous white-space
stripped off. I found it convenient to strip off the package specifier
"utf8::". To to so, the code simply pretends "lookup_name" begins just
after the "utf8::", and adjusts various other values to compensate.
However, it missed the adjustment of one required one.
This is only a problem when the property name begins with "perl" and
isn't "perlspace" nor "perlword". All such ones are undocumented
internal properties.
What happens in this case is that the input is reparsed with slightly
different rules in effect as to what is legal versus illegal. The
problem is that "lookup_name" no longer is pointing to its initial
value, but "name" is. Thus the space allocated for filling "lookup_name"
is now shorter than "name", and as this shortened "lookup_name" is
filled by copying suitable portions of "name", the write can be to
unallocated space.
The solution is to skip the "utf8::" when reparsing "name". Then both
"lookup_name" and "name" are effectively shortened by the same amount,
and there is no going off the end.
This commit also does white-space adjustment so that things align
vertically for readability.
|
|
Tested by deraadt@
|
|
ok deraadt@
|
|
Reported and suggested by jsing@
|
|
|
|
so instead of shipping the file internally, let's generate it and
install it with the rest of the headers; unbreaks xenocara build
|
|
|
|
|
|
|
|
|
|
(see user_caps(5))
also obviously protects the term name just in case someone wants to have
fun with it..
|
|
|
|
as noticed by afresh1@
(this should be all for now)
|
