Fix return value for some invalid UTF-8 byte sequences
Update the length definitions to honor RFC 3629 (from 2003):
o The octet values C0, C1, F5 to FF never appear.
Add a check that continuation bytes are valid when adding them to the
internal buffer so that an out-of-bytes error doesn't override the
"invalid bytes" error.
Fixes PR 60369 by Bruno Haible.
Pull up the following revisions, requested by martin in ticket #337:
src/usr.sbin/sysinst/configmenu.c 1.25
src/usr.sbin/sysinst/install.c 1.26
src/usr.sbin/sysinst/net.c 1.47
src/usr.sbin/sysinst/upgrade.c 1.22
We have SSL trust anchors in base, so make use of them when downloading
additional items after basic installation is done (even if the installer
used does not come with its own certs, so we can not verify trust
for set download).
Pull up the following revisions, requested by martin in ticket #336:
src/usr.sbin/sysinst/msg.mi.de 1.59
src/usr.sbin/sysinst/msg.mi.en 1.60
src/usr.sbin/sysinst/msg.mi.es 1.50
src/usr.sbin/sysinst/msg.mi.fr 1.53
src/usr.sbin/sysinst/msg.mi.pl 1.56
src/usr.sbin/sysinst/util.c 1.84
Include "tests" and "manhtml" in the optional sets.
Pull up the following revisions, requested by martin in ticket #335:
src/usr.sbin/sysinst/Makefile.inc 1.54
src/usr.sbin/sysinst/configmenu.c 1.24
src/usr.sbin/sysinst/defs.h 1.96
src/usr.sbin/sysinst/main.c 1.37
src/usr.sbin/sysinst/menus.mi 1.31
src/usr.sbin/sysinst/net.c 1.46
When compiled with SMALLPROG (i.e. as part of a crunched ramdisk
userland) ftp(1) does not support https - so remove that option from
sysinst and only offer http in that case.
Should fix PR 60359.
PR bin/59635 - src/usr.bin/mail: fix post realloc() cleanup
This is a rather hackish solution, much better would be to abandon the
pointers altogether, and simply use message offsets (ints) into the array
to provide the relationships between messages.
Or abandon the message array (and the need for realloc() along with it)
and replace it with a list.
Both methods would achieve the aim of getting rid of the need to go and
massage the data to keep things correct when a realloc moves things around.
Either would require more changes in more places that this crude change,
and to get this done before -11 gets released, the few changes the better.
Another possibility would be to just revert to the adjustment method used
in -10 (which looks like it should work to me - but I don't know why it
was changed).
[4 lines not shown]
We have SSL trust anchors in base, so make use of them when downloading
additional items after basic installation is done (even if the installer
used does not come with its own certs, so we can not verify trust
for set download).
When compiled with SMALLPROG (i.e. as part of a crunched ramdisk userland)
ftp(1) does not support https - so remove that option from sysinst and
only offer http in that case.
Should fix PR 60359.
Pull up the following revisions, requested by martin in ticket #327:
src/usr.sbin/sysinst/util.c 1.81
src/usr.sbin/sysinst/arch/evbarm/md.c 1.24
src/usr.sbin/sysinst/arch/evbarm/md.h 1.10
PR 60360: make the default /boot partition on evbarm 64MB if we need
the dtb set (the newer dtb files overflow the old 32mb default).
In ACPI environments where we do not need dtb installed, do not select
the set by default.
acpi(4): Leave Hyper-V rndsource attached.
This way, it will be reported through rndctl(8) rather than only by
grepping through dmesg, and rndctl(8) can control it, e.g. if it
turns out something is wrong with that but not with RDSEED on the
same virtual CPU, you can use `rndctl -Ed "Hyper-V OEM0"' to discount
it and the system will gather fresh samples from RDSEED instead.
The same problem could in principle happen with other removable
rndsources like ualea(4), and we don't really have a good way to deal
with that -- either to configure the system up front to discount a
hot-pluggable rndsource that hasn't yet been plugged in, or to
retroactively discount a removable rndsource that was already
removed. But this one isn't hot-pluggable or removable, so keeping
it around is enough to sidestep this problem.
ld.elf_so(1): Run concurrent dlopen/dlclose test a few more seconds.
More likely to provoke the problem this way. Still not 100% reliable
because the problem is a race condition, but better than having the
test unexpectedly pass half the time.
Also set a timeout of 20sec, since I've seen the test get into an
infinite loop sometimes and it's now supposed to complete in 5sec +
epsilon.
PR lib/59751: dlclose is not MT-safe depending on the libraries unloaded
Pull up the following revisions, requested by martin in ticket #324:
usr.sbin/sysinst/util.c 1.82,1.83
PR 60354: move the test and new message about optional sets missing
into the correct place so it only shows the message when we really
can not find the set.
This only applies to local files.
PR 60354: fix a stupid mistake in the previous change:
move the test and new message about optional sets missing into the
correct place so it only shows the message when we really can not
find the set.
ppp(4): Use 32-bit timeouts, not 64-bit timeouts.
The timeouts are checked every 15sec so there is no real need to
record starting and ending times in units of seconds with more than 5
bits of precision. So 32-bit starting and ending times are more than
enough. And there is surely no need for decades-long timeouts.
1. Clamp the timeouts in SPPPSETIDLETO(struct spppidletimeout) and
SPPPSETKEEPALIVE(struct spppkeepalivesettings) to INT32_MAX/2,
which is over 34 years worth of seconds.
(We should never have spent any effort on time_t compat for these:
we should have just left them at 32-bit! Oh well.)
2. Use time_uptime32, not time_uptime, since 32-bit unsigned
arithmetic is large enough to handle all the differences we will
encounter when timeouts are clamped to INT32_MAX/2 without any
risk of trouble from wraparound.
PR kern/60364: if_spppsubr.c uses nonportable 64-bit atomics
