Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
ok bluhm inoguchi
|
|
|
|
userland the TDBs which exceeded hard limit.
Also the `ipsec_notdb' counter description in header doesn't math to
netstat(1) description. We never count `ipsec_notdb' and the netstat(1)
description looks more appropriate so it's used to avoid confusion with
the new counter.
ok bluhm@
|
|
tee(1) handles partial writes correctly, but the more idiomatic write
loop is shorter and easier to audit than this heterodox approach.
ok millert@
|
|
This is three times the same thing while genrsa needs some extra steps
to deal with opaque BIGNUMs. We can also garbage collect some Win 3.1
contortions and use the conversion routines directly instead of doing
them manually.
ok jsing
|
|
|
|
|
|
for RSA keys). Avoids fatal errors for PKCS#11 libraries that return
empty keyid, e.g. Microchip ATECC608B "cryptoauthlib"; bz#3364
|
|
ca certs but not with simple key lifetimes within the allowed
signers file.
Since it returns the first keys principal it finds this could
result in a principal with an expired key even though a valid
one is just below.
patch from Fabian Stelzer; feedback/ok djm markus
|
|
|
|
|
|
ok deraadt millert
|
|
as half-close on the output side; ok deraadt millert
|
|
POSIX.1-2008 tweaked the uniq definition in light of AGI 1003.1-2001
#133. uniq must now *ignore* the trailing newline when comparing
lines from the input.
In practice this means that if the last line in the input is missing a
trailing newline it isn't necessarily different from the line
preceding it.
So, uniq(1) now stubs the trailing newline before doing any line
comparisons.
For sake of simplicity, this patch introduces a second change: if the
last line in the input is missing a trailing newline and we choose to
print the line, a newline is appended when we print it.
Adopting the newline change aligns our implementation with with
POSIX.1-2008 (which we already claim in the manpage). Adopting both
changes aligns our behavior with that of FreeBSD and GNU uniq. For
better or worse, OpenBSD's uniq no longer behaves like NetBSD's uniq
in this corner case.
References:
POSIX.1-2001 uniq:
https://pubs.opengroup.org/onlinepubs/009695399/utilities/uniq.html
Austin Group Interpretation 1003.1-2001 #133:
https://collaboration.opengroup.org/austin/interps/documents/14355/AI-133.txt
POSIX.1-2008 uniq:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/uniq.html
--
Discussed with millert@. With input from schwarze@. Positive feedback
from bcallah@.
Thread: https://marc.info/?l=openbsd-tech&m=163581613829524&w=2
ok millert@
|
|
interferes with the new poll()-based listen loop; spotted and
debugged by anton@+deraadt@
|
|
If the "file" argument to cnt() is NULL and we call warn(3) we will
get a NULL dereference.
Change the name of the argument to "path" and make "file" a local
variable. Ensure that we set "file" to a valid C-string, even if
"path" is NULL.
While we're here, const the file name pointers, too.
Thread: https://marc.info/?l=openbsd-tech&m=163708784422157&w=2
ok millert@
|
|
modes and current editing position and at the command prompt. It is
invisible but this is helpful for people using screen readers. GitHub
issue 2970.
|
|
with djm
|
|
|
|
ok djm
|
|
to make things easier.
back and forth and ok; djm
|
|
Discussed with mestre
|
|
We already had the fix so no actual code changes.
|
|
|
|
|
|
select() code was using exceptfds incorrectly..
ok millert
|
|
window name, GitHub issue 2964.
|
|
quarter of the space; from Alexis Hildebrandt.
Also new sentence, new line in tmux.1, from jmc.
|
|
|
|
same promises, just call it once before the switch case while at the same time
hoisting one unveil(2) so they are all grouped.
The call to pledge(2) on file() can also be simplified since "stdio rpath getpw"
will already be activated when we reach it.
OK deraadt@
|
|
patch from Jan Stary <hans at stare dot cz>;
OK martijn@
|
|
I overlooked the autoinstall case where "Requesting ..." is used,
but those messages that got fixed where omitted in ftp's SMALL version.
Noticed the hard way by anton
|
|
Streamlined NTRU Prime post-quantum KEX to the default KEXAlgorithms
list (after the ECDH methods but before the prime-group DH ones).
ok markus@
|
|
feedback/ok markus@
|
|
prepare bc(1) and dc(1) for opaque BIGNUMs.
"looks sane" otto
|
|
ok millert
|
|
Encoding URL paths changes the requested URL and therefore may yield
different responses (opposed to an unencoded URL), solely depending on how
the server implements de/encoding.
Always print the encoded URL which actually gets requested in output like
"Requesting ..." and erors likes "Error retrieving ....: 404 Not Found"
and don't use the original URL provided on the command line.
This matches exactly what is seen on the wire, e.g. with tshark(1) and
helps debugging URL de/encoding related (server) issues.
Feedback OK sthen
|
|
user that doesn't exist; better matches what the shell does
ok deraadt@
|
|
|
|
.text.* are generated when using -ffunction-sections.
makes nm(1) to correctly identify the function symbols as N_TEXT.
found while debugging librsvg build error, where some symbols where not found by libtool(1) (which is using nm(1)).
ok gkoehler@
|
|
RFC 1738 Uniform Resource Locators (URL) lists tilde as unsafe character.
RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax updates it to
The tilde "~" character was added to those in the "unreserved" set,
since it is extensively used on the Internet in spite of the
difficulty to transcribe it with some keyboards.
In theory, this shouldn't make a difference, but some servers do not decode
"%7e" and thus erroneously serve a 404.
RFC 2396 2.4.2. When to Escape and Unescape says:
In some cases, data that could be represented by an unreserved
character may appear escaped; for example, some of the unreserved
"mark" characters are automatically escaped by some systems. If the
given URI scheme defines a canonicalization algorithm, then
unreserved characters may be unescaped according to that algorithm.
For example, "%7e" is sometimes used instead of "~" in an http URL
path, but the two are equivalent for an http URL.
Update ftp(1) to RFC 2396 by no longer treating "~" as unsafe character.
This is effectively a one-character diff; update comments accordingly as
well as the order of characters to ease code-to-standard comparison.
This matches curl(1) and wget(1) behaviour wrt. encoding of "~".
OK sthen
|
|
PR#283, ok markus@
|
|
running with the -M option or with a MANPATH environment variable
that has neither a leading or trailing ":" nor any "::". If -M or
MANPATH override the configuration file rather than adding to it,
just ignore any "manpath" directives while processing the configuration
file.
This fixes a bug reported by Jan Stary <hans at stare dot cz>
on misc@.
|
|
no code change
|
|
Replace hand-rolled parentheses with the proper mdoc(7) macro,
otherwise the closing ")" ends up inside the command description.
Reported by Josh Rickmar, thanks!
|
|
|
|
|