Age | Commit message (Collapse) | Author |
|
3055.
|
|
Like set-clipboard and allow-rename it is safer to forbid this by
default.
|
|
query.
|
|
|
|
spotted by HARUYAMA Seigo
|
|
|
|
The lookup tables in tr(1) are called "string1" and "string2". This is
misleading:
- They aren't C strings, they are lookup tables.
- The names "string1" and "string2" don't hint at what their contents
actually mean. The meaning of a given table changes with tr(1)'s
operating mode. There are five different modes.
It would be considerably easier to see what is happening at a glance
if the tables were named for their corresponding byte transformation.
So instead of two tables named "string1" and "string2" we'll have
three tables named "delete", "squeeze", and "translate". In addition,
the "string" passed to the setup() function will be called a "table".
With this patch the code in main() is way easier to understand.
Hopefully this makes subsequent patches easier to review.
Thread: https://marc.info/?l=openbsd-tech&m=164355980600901&w=2
No complaints on tech@ after over a week.
|
|
Found by the Valgrind tests on github, ok deraadt@
|
|
sparc64. Use memcpy() to align the data.
found by regress/usr.bin/ctfdump; OK mpi@
|
|
We're only reading one file here, so unveil(2) is overkill. We can
achieve the same effect with just pledge(2):
- Start with an initial pledge(2) of "stdio rpath" at the top of main().
We know we need to read a file at this point but don't yet know which
one.
- Drop the pledge(2) down to "stdio" after we open(2) and fstat(2) the
chosen file.
- Dropping "rpath" obviates unveil(2).
Thread: https://marc.info/?l=openbsd-tech&m=164437072017248&w=2
ok millert@
|
|
|
|
> revision 1.106
> date: 2021/10/15 14:46:46; author: deraadt; state: Exp; lines: +13 -9; commitid: w5n9B2RE38tFfggl;
> openbsd 7.0 release shipped with the (hopefully last) scp that uses RCP
> protocol for copying. Let's get back to testing the SFTP protocol.
This will be put back once the OpenSSH release is done.
|
|
Found by robert@
|
|
It feels more natural to me to use -a directly when asking mandoc(1)
to use a pager. The reason that "mandoc -l" does exactly the same
as "mandoc -a" is that "mandoc" is essentially "man -lc", so the -a
implied by -l negates the -c and the -l has no effect because it is
already the default for mandoc(1).
The more usual command for doing the same is "man -l foo.1 bar.1 ..."
but that's off-topic for the mandoc(1) manual page.
Patch on tech@ from Anders Damsgaard <anders at adamsgaard dot dk>.
|
|
We don't need "rpath" if we're only processing the standard input.
Thread: https://marc.info/?l=openbsd-tech&m=164433848419371&w=2
ok deraadt@ millert@
|
|
Historicallly, hpdelim accepted ":" or "/" as a port delimiter between
hosts (or addresses) and ports. These days most of the uses for "/"
are no longer accepted, so there are several places where it checks the
delimiter to disallow it. Make hpdelim accept only ":" and use hpdelim2
in the other cases. ok djm@
|
|
- Output errors are terminal.
- Input errors yield a warning and cause head(1) to fail
gracefully.
Tweaked by millert@.
Thread: https://marc.info/?l=openbsd-tech&m=164419238123928&w=2
ok millert@
|
|
hashing data outselves. Saves a fair bit of code and makes life easier
for some -portable platforms.
|
|
ok jmc@ sthen@ millert@
|
|
types, from Thomas Adam.
|
|
public keys so that they will be tried last. From github PR#295 from
"ProBackup-nl", ok djm@
|
|
|
|
|
|
the code. Also add error checking where possible.
ok jsing
|
|
ok jsing
|
|
3050.
|
|
3054.
|
|
|
|
|
|
in allowed_signers files; from Fabian Stelzer
|
|
static const char *array => static const char * const array
from Mike Frysinger
|
|
messages. Spotted by and ok tb@
|
|
the items. Also fix mode menus.
|
|
from Marcel Partap.
|
|
|
|
|
|
It's no longer needed since the child will get terminated by the SIGTERM
to the process group that cleans up any auth helpers, it simplifies
the signal handler and removes the risk of a race when updating the PID.
Based on analysis by HerrSpace in github PR#289, ok djm@
|
|
The main loop here is horribly obfuscated. In particular, the path
through the loop to exit(3) is very complex.
Refactor the open/read/write/close portions of the loop out of main()
into a separate function, head_file().
The result is a lot easier to understand at a glance. In particular,
the path to the end of main() is now dead simple.
Thread: https://marc.info/?l=openbsd-tech&m=164325900400701&w=2
ok millert@
|
|
The main loop here is obfuscated.
Refactor the open/read/write/close portion of the loop out of main ()
and into a new function, rev_file(). Move "multibyte" out into global
storage.
The result is much easier to understand at a glance.
Thread: https://marc.info/?l=openbsd-tech&m=164329515201417&w=2
ok millert@
|
|
This conditional chain short-circuits if futimens(2) fails, leaving the
file descriptor open. We need to evaluate each system call in the chain
separately to ensure we attempt to close(2) the descriptor.
With input from guenther@ and millert@.
Thread: https://marc.info/?l=openbsd-tech&m=164332809900558&w=2
ok millert@, probably ok guenther@
|
|
apostrophe.
|
|
Fixes error handling in closefile() and closeall(). Long standing
warnings had been made fatal and some fatal errors went undetected.
|
|
directly into the transport input buffer.
Use this in the client and server mainloops to avoid unnecessary
copying. It also lets us use a more greedy read size without penalty.
Yields a 2-3% performance gain on cipher-speed.sh (in a fairly
unscientific test tbf)
feedback dtucker@ ok markus@
|
|
rather than into a stack buffer that needs to be copied again;
Improves performance by about 1% on cipher-speed.sh
feedback dtucker@ ok markus@
|
|
sshbuf; ok markus@
|
|
quit_pending; no functional change but saves a bunch of boilerplate
|
|
spotted by dtucker@
|
|
not cleared. There are subtle errors in various programs.
In this particular case, the program should error out.
ok djm millert
|
|
strtonum() is only called to verify that a string is numerical, the
return value is unused.
inlist is no longer used after the code was refactored.
ok millert@ guenther@
|
|
of Z_PARTIAL_FLUSH as the latter is not actually specified as a valid
mode for inflate(). There should be no practical change in behaviour
as the compression side ensures a flush that should make all data
available to the receiver in all cases.
repoted by lamm AT ibm.com via bz3372; ok markus
|