libssl: use correct alert for key_share without supported_groups
Processing the key_share extension requires a supported_groups extension.
RFC 9846, section 9.2 explicitly mandates a missing_extension alert in
this situation, so use that instead of illegal_parameter.
We do have code in tls13_client_hello_required_extensions() implementing
the requirements on extensions of the relevant paragraph of that section
with the corrrect alerts. The error in the extension processing happens
before hitting these checks in this particular case.
Reported by Tom Gouville of the tlspuffin team as part of
https://github.com/libressl/portable/issues/1279
ok jsing kenjiro
Ensure numbering is repainted after completion redraw.
Fixes screen corruption when using completion if line numbering is
enabled. Otherwise, the completion area is redrawn without line
numbers. From Jeffrey Johnson
I noticed boot-time /tmp pruning could take a substantial amount of time.
The purpose is two-fold, to remove cruft, and stop newly authenticated users
from seeing it. Took about 20 drafts to get it right. The /tmp files
are now pushed into a mktemp directory, then deleted async, except a few are
removed immediately for the case of the filesystem being full. After daemon
startup has completed, we wait for the removal job to complete (let's keep an
eye on this, because it is possible we actually don't need to wait)
draft iterations with millert, afresh1, and dgl
Fix a weird seventeen-year-old documentation bug where the descriptions
of the \*(lp and \*(rp predefined strings were exchanged.
Nobody noticed because all predefined strings are obsolete anyway.
Patch from Alexander Ziaee <ziaee at FreeBSD.org>.
avoid needlessly discarding a const qualifier in a pointer assignment;
no functional change; small ugliness found in a build log
sent in by Xose Vazquez Perez <xose.vazquez at gmail.com>
If writing a file fails, propagate the error to the server via a new
message. Use a client flag rather than bumping the protocol version.
GitHub issue 5451.