Provide assembly implementation of SHA-512 for amd64 in libc
Provide a generic assembly implementation for SHA-512 - this is
considerably faster than the C version.
Largely borrowed from libcrypto.
With input from naddy@
ok naddy@ tb@
Provide assembly implementation of SHA-256 for aarch64 in libc
Provide a CE assembly implementation that can be used on hardware that
has the CE SHA-256 instructions. This is considerably faster than the
generic C implementation.
Largely borrowed from libcrypto.
With input from naddy@
ok tb@
SparcAsmParser: fix off by one and allow %r31 to be used
rust contains a sparc64.s file with
.cfi_register %r15, %r31
This fails with 'src/arch/sparc64.s:59:26: error: invalid register name'
Changing RegNo < 31 to RegNo <= 31 fixes this.
ok kettenis kirill
Do not use <br/> inside <pre> because it causes ugly formatting.
Bug reported long ago by Mohamed Akram <mohd.akram at outlook.com>.
Patch from Michael Stapelberg <stapelberg at debian.org>.
Provide assembly implementations of SHA-256 for amd64 in libc.
Provide a generic assembly implementation for SHA-256 - this is
considerably faster than the C version.
Provide a SHA-NI assembly implementation that can be used on hardware that
has the SHA-NI instructions. This is considerably faster than the generic
assembly implementation.
Both are largely borrowed from libcrypto.
With input from naddy@
ok naddy@ tb@
Simplify handling of remaining record content on switch to legacy stack.
Now that the legacy stack uses struct tls_content, store any remaining
record content directly, rather than fudging up a record that the legacy
stack will process on the next read.
ok kenjiro@ tb@
Allocate TLS 1.3 receive buffers lazily
The receive buffer is not used for records created for sending. Avoid
allocating a maximum-sized buffer in tls13_record_new() and instead
allocate a header-sized buffer when tls13_record_recv() is first called.
The buffer will grow as needed once the record length is known.
This avoids an unnecessary allocation for outgoing records and reduces
the initial allocation size for incoming records.
ok tb jsing
init(8): remove support for the window= field in /etc/ttys
This feature was introduced in 4.3BSD, and announced in "Bug Fixes
and Changes in 4.3BSD", dated April 15, 1986. The feature provided
a way to start a window system associated with a tty before
starting getty(8).
However the implementation has a few negatives and these days
graphical environments are better started in other ways.
In particular:
- the window command is run with root privileges
- init(8) does not track or supervise the process as part of the
tty session.
- reloading /etc/ttys by sending SIGHUP to init, can leave a stale
window command cached incorrectly
- repeated reloads leak memory
Rather than fix all these issues, remove the feature instead.
[5 lines not shown]
llvm/sparc64: match BFD -N alignment
BFD aligns nonpaged PT_LOAD segments to their maximum contained section
alignment. Do the same for SPARCV9 instead of retaining the 1 MiB
maximum page alignment.
This removes roughly 1 MiB of leading padding from ofwboot without
changing its load address or memory layout.
OK: deraadt@, kettenis@
Overhaul printing of whitespace before tbl(7) in man(7).
This is the last major piece i intend to put in for making mandoc(1)
compatible with groff-1.23.
In spite of the change in man_term.c 1.194 (August 2022)
which removed unconditional vertical space before .TS,
GNU eqn(1) still prints vertical space in some cases
where the layout contains vertical lines.
TIOCGSID can dereference a freed t_session, because we are storing s_leader
in the wrong place. This is a cold hard crash crashes. Some folk are
looking at fixing this properly but it will take some time, so in the meantime
we should just fail the ioctl.
from deraadt@; from Acts1632, OK kettenis@
this is errata/7.9/013_ttyioctl.patch.sig
TIOCGSID can dereference a freed t_session, because we are storing s_leader
in the wrong place. This is a cold hard crash crashes. Some folk are
looking at fixing this properly but it will take some time, so in the meantime
we should just fail the ioctl.
from deraadt@; from Acts1632, OK kettenis@
this is errata/7.8/049_ttyioctl.patch.sig
sysctl_proc_args() did not check if uvm_io() returned no data, which
could result in uninitialised memory being returned. Rather than callers
of uvm_io() having to carefully check for this condition, treat it as an
error.
from dgl@; OK kettenis@; initial report from Acts1631
this is errata/7.9/012_kernproc.patch.sig
sysctl_proc_args() did not check if uvm_io() returned no data, which
could result in uninitialised memory being returned. Rather than callers
of uvm_io() having to carefully check for this condition, treat it as an
error.
from dgl@; OK kettenis@; initial report from Acts1631
this is errata/7.8/048_kernproc.patch.sig
