| Age | Commit message (Collapse) | Author |
|---|
|
via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800,
but fixing two bugs in his description.
This commit also includes a few minor improvements to the description
of DES_fcrypt(3), also from OpenSSL, tweaked by me.
|
|
Makes stuff like
limit 1500000 usec
work correctly.
ok millert@ tb@
|
|
ok millert@ tb@
|
|
sort dependencies so that at least this is 100% reproducible...
|
|
|
|
These functions constitute an obvious portability nightmare,
but that's no excuse for incorrect documentation.
Pointed out by Nicolas Schodet
via OpenSSL commit b713c4ff Jan 22 14:41:09 2018 -0500.
|
|
from Hubert Kario <hkario at redhat dot com>
via OpenSSL commit 681acb31 Sep 29 13:10:34 2017 +0200.
|
|
from Rich Salz via OpenSSL commit 8162f6f5 Jun 9 17:02:59 2016 -0400.
Merging the RETURN VALUES section really wouldn't make much sense
here, it contains no additional information and i don't see any way
to reorganize the content and make it better.
|
|
Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
by Paul Yang, but reworded for intelligibility and precision.
While here, also expand the description of the "ret" argument of
BIO_callback_fn(). That's a fairly complicated and alarmingly
powerful concept, but the description was so brief that is was
barely comprehensible.
|
|
be fair to those servers, display a more accurate message of what we know
|
|
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
with tweaks by me.
|
|
from Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800.
|
|
From Paul Yang via OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
with one tweak.
|
|
from semarie@, ok benno@
|
|
This should make tests following a failing test pass.
|
|
accordingly. Make some statements more precise, and point out
some dangerous traps in these ill-designed interfaces.
Also do some minor polishing while here.
Triggered by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800
by Paul Yang, but not using most of his wording because that is in
part redundant, in part incomplete, and in part outright wrong.
|
|
In order to have reproducible tests route entries must not stay. Otherwise
the 'Use' counter keeps growing.
|
|
is created, it gets default IPv6 addresses. So reflect that change
in netinet6 outputs.
|
|
the last snaphot.
|
|
|
|
this is a port of the change made to if_etherip.c r1.35 to allow
addresses to be configured before the tunnel is configured.
|
|
this is a port of the change made to if_etherip.c r1.35 to allow
addresses to be configured before the tunnel is configured.
this rollback is particularly annoying on gre with keepalives.
keepalives rely on the interface rdomain and tunnel rdomain to be
the same, which the rolled back semantics checked. now it is possible
to create an invalid configuration and not get any feedback about
it.
|
|
this is a port of the change made to if_etherip.c r1.35 to allow
addresses to be configured before the tunnel is configured.
|
|
this avoids allocating a mobileip_softc on the stack to build a key
for looking up interfaces with on packet input. struct ifnet inside
mobileip_softc is "quite large", and may blow the 2k limit one day.
|
|
our network drivers have a feature where if you configure an address
on the interface, it implicitly brings the interface up. i changed
etherip so you could only change the tunnel configuration while it
down, but maintained the implicit up behaviour. bringing the tunnel
up also relied on having valid configuration, ie, tunnel addreses
must be configured otherwise up will fail.
this means people who have address config in their hostname.etherip
files before config for the tunnel addresses will have problems.
firstly, the address wont be configured because falling through to
the interface up fails because the tunnel isnt configured correctly,
and that error makes the address config roll back. secondly, config
that relies on configuring the address to bring the interface up
will fail because there's no explicit up after the tunnel config.
this diff rolls the tunnel config back to keeping the interface on
a list, and allowing config at any time. the caveat to this is that
it makes mpsafety hard because inconsistent intermediate states are
visible when packets are being processed.
|
|
to sometimes mean "character set", which conflicts with the normal
meaning of "optional element" in manual pages. While here, add a
few related clarifications and tweak a few details.
Triggered by a minor bug report from <trondd at kagu-tsuchi dot com>,
and by bentley@ subsequently pointing out the abuse of [].
Patch using input from jmc@, who also agreed with some previous versions.
|
|
|
|
|
|
|
|
the interface's address and thus the cached configuration data becomes
invalid and must be discarded.
Issue found & fix tested by Christer Solskogen. Thanks!
|
|
ok mpi@ who will investigate.
|
|
The signal handlers from the original ssh1 code on which OpenSSH
is based assume unreliable signals and reinstall their handlers.
Since OpenBSD (and pretty much every current system) has reliable
signals this is not needed. In the unlikely even that -portable
is still being used on such systems we will deal with it in the
compat layer. ok deraadt@
|
|
memory regions.
|
|
consistent across architectures.
Requested by deraadt@
ok kettenis@
|
|
stack frame format has changed. Apparently AAPCS doesn't specify
at all what a stack frame looks like. We end up with much simpler
code, but also with a lot less information in the trace.
ok kettenis@
|
|
as requested by jsing@, and also document six more related functions
that have already been public before that.
OpenSSL fails to document any of these.
|
|
SDIO function. This is necessary for some SDIO cards that need to be
talked with using smaller block lengths than the maximum supported by
the host controller.
ok kettenis@
|
|
interface for "reading memory" akin to the bus_space(9) API. The
already existing multi interface is used for "reading FIFOs". The
technical difference is that one always reads from the same address
(FIFO) while the other increments the address while reading (memory).
ok kettenis@
|
|
|
|
|
|
shown columns. There's still parts that could do with a good polishing,
but it's an improvement.
OK tedu@
|
|
ok dlg@
|
|
|
|
don't fault on strict alignment architectures.
|
|
alignment can be variable, it's better to move taking care of alignment
into the BCDC receive code.
|
|
|
|
receive. Did that everywhere else but missed it here.
|
|
this attribute. The kernel does so for main-process stacks at execve() time,
pthread stack functions do so for new stacks, and stacks provided to
sigaltstack() and other user-provided stacks will need to be allocated
in that way.
Not required yet, but paving the way.
Work done with stefan
|
|
|
|
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.
Prompted by tb@
|
