Merge in a number of upstream changes from Bouffalo, resolving
conflicts. Most conflicts came from warring whitespace fixes, which is
better than no whitespace fixes in either repo. I generally took the
upstream version in such cases to make future merges easier.
I have left out all upstream docs changes from this merge, since those
will have to be separately merged into our bl602-docs submodule.
image_conf, make_scripts_riscv - Delete trailing spaces. Change tabs to 4 space multiples.
.c and .h get tabs expanded to four spaces for consistency, traliing whitespace whacked.
Makefiles do NOT get tabs changed.
The ipv6cp-accept-local option was supposed to enable it, but it is
already enabled by default, with no way to disable it.
For coherency with IPv4 and IPX, this disables ipv6cp-accept-local by
default, and the option can be used to enable it.
This also enables it automatically when the local id is not
specified, in coherency with IPv4 and IPX, and as the documentation was
saying.
Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
The ipv6cp-accept-local option was supposed to enable it, but it is
already enabled by default, with no way to disable it.
For coherency with IPv4 and IPX, this disables ipv6cp-accept-local by
default, and the option can be used to enable it.
This also enables it automatically when the local id is not
specified, in coherency with IPv4 and IPX, and as the documentation was
saying.
Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
This adds some basic checks to the subroutines of eap_input to check
that we have requested or agreed to doing EAP authentication before
doing any processing on the received packet. The motivation is to
make it harder for a malicious peer to disrupt the operation of pppd
by sending unsolicited EAP packets. Note that eap_success() already
has a check that the EAP client state is reasonable, and does nothing
(apart from possibly printing a debug message) if not.
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
This adds some basic checks to the subroutines of eap_input to check
that we have requested or agreed to doing EAP authentication before
doing any processing on the received packet. The motivation is to
make it harder for a malicious peer to disrupt the operation of pppd
by sending unsolicited EAP packets. Note that eap_success() already
has a check that the EAP client state is reasonable, and does nothing
(apart from possibly printing a debug message) if not.
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
