Age | Commit message (Collapse) | Author |
|
|
|
include various system headers (mostly stdlib.h); include them
explicitly
|
|
ed25519 which is supported when built without OpenSSL.
|
|
not since
|
|
https://github.com/openssh/openssh-portable/pull/144 by Ed Maste
|
|
|
|
OK millert
|
|
ok millert@, sf@, deraadt@
|
|
the following improvements:
- Character at position CB is 'E' with diaeresis, not with tilde (12x24 version)
- Character at position D6 is 'O' with diaeresis, not with tilde (12x24 version)
- Character at position DC is 'U' with diaeresis, not with tilde (12x24 version)
- Fix middle bar thickness in the upper case 'eth' character (12x24 version)
- Fix ring alignment for the 'A' and 'a' characters (16x32 and 32x64 versions)
- Fix tilde alignment in the 'o' with tilde character (32x64 version)
- Remove strain pixel on the '3' and 'k' characters (32x64 version)
OK deraadt@, mpi@
|
|
found obscure. Repair a broken WangTEK 5150ES quirks entry that
apparently suffered some damage when imported in 1995. It never made
NetBSD/FreeBSD quirk lists at all.
Some whitespace tweaking to make everything line up.
|
|
At the moment it only supports disabling the watchdog, which lets me
continue to work on the Turris Mox.
ok kettenis@
|
|
|
|
Result is a crash at power down. Skip the activate function if
attach has failed. Solution taken from ehci(4).
OK deraadt@ kettenis@
|
|
devices with quirks.
|
|
|
|
For a small proportion of frames on 8265 we have observed firmware reporting
"not encrypted" even though in Wireshark these frames appear as regular
encrypted frames (rx_pkt_status=0xc0400007 type=0x8 subtype=0x80 m_len=1542).
This causes frame drops which do not occur with software crypto.
We might try again after a firmware upgrade. There seems to be no public
record of bug fixes made by Intel between firmware versions which degrades
our development process into pure trial-and-error. We need to waste our own
time to find out information which Intel should be providing to the public.
If anyone is aware of a source of such information, please let us know.
All this is of course very disappointing.
Problem reported by and debugged with help from solene@
|
|
Based on OpenSSL 1.1.1b.
ok inoguchi@ tb@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
From OpenSSL 1.1.1b.
ok tb@ inoguchi@
|
|
|
|
I don't think there ever was a reason for doing so.
Besides, there is a discrepacy with respect to the point in the
document affected. That flag controls whitespace at the current
formatting point. But when HTML_BUFFER is in effect, the line break
and indentation is typically inserted one word further to the left.
Anything happening at that point to the left can't reasonably
influence spacing at the different point further to the right.
Among other effects, this change avoids some spurious line breaks
in HTML code at points where they weren't supposed to happen, line
breaks that in some cases caused undesirable, visible whitespace
when the resulting HTML was rendered.
|
|
their "CIPHER ST150S (old drive)" devices back.
|
|
|
|
ok patrick@
|
|
them. Based on patch from Jakub Jelen; bz#2430 ok markus@
|
|
multiple ARP packets to a remote machine with Scapy. Check ARP
replies, table entries and log messages. All log messages in
in_arpinput() are generated. Proxy ARP is also tested.
|
|
the way up to dispatch_run_fatal() and lose all meaninful context
to help with bz#3063; ok dtucker@
|
|
|
|
If the NIC is in some error state (seen on a i219LM when em_read_phy_reg_ex()
returns at "MDI Error"), it can happen that we loop endlessly because the loop
variable is modified again somewhere down in the call stack. Use a separate
variable to make the attach fail with "Hardware Initialization Failed" instead
of hanging.
yes deraadt@
|
|
|
|
|
|
This simplifies the code and allows any block size multiple of 1ms to
be used when play and recording number of channels are not the same.
ok mpi@
|
|
This simplifies the code and allows any block size supported by the
hardware to be used.
ok mpi@
|
|
The first sets the block size in frames, which is necessarily common
to play and recording directions no matter the number of channels. The
second sets the number of blocks per buffer for the given
direction. Together, these two functions allow audio drivers to easily
set the block size, matching both playback and recording constraints.
The round_blocksize() didn't allow to do so because it returns the
block size in *bytes*. Since the driver doesn't know if it's called
for the play or for the record block size, it's impossible to
calculate the block size in all cases if play and record number of
channels are different.
ok mpi@
|
|
|
|
of soft interrupts are lower than priorities of hard interrupts.
This allows the delivery of hard interrupts while soft interrupts
are masked.
|
|
rename to make more consistent with philosophically-similar auth
options parsing API.
|
|
ok kettenis
|
|
|
|
|
|
So fold 'modeflags' field of st_softc into 'flags' field of same. Nuke
a bunch of dubious/obvious comments.
|
|
|
|
implmentation does not care about ICMPv6, it simply adds static
multicast routes. Multicast routing needs at least two test machines.
Otherwise only send and receive on localhost is tested.
Currently receiving link-local packets via loopback does not work
due to wrong scope id.
Everything is mostly copied from IPv4 regress.
|
|
num calculations and avoids lots of ugly output to stdout. Remove
fflush(3) of stderr, it is unbuffered anyway.
with Moritz Buhl
|