Hi Anton,
Thanks for providing those links to the past discussion.
Anton Lindqvist wrote:
> As I would address this, the numbers of arguments passed to the
> completion related routines is already painfully^W long. I would rather
> take a step back and introduce a `struct globstate' (just an exa
On Tue, Nov 10, 2020 at 06:49:28PM +0100, Sven M. Hallberg wrote:
> Apologies for jumping in as a bystander, but if I may comment:
>
> Anton Lindqvist on Tue, Nov 10 2020:
> > Been brought up before[1] and rejected[2][3].
>
> Anton Lindqvist on Sun, Jul 02, 2017:
> > diff below in which slashes a
Apologies for jumping in as a bystander, but if I may comment:
Anton Lindqvist on Tue, Nov 10 2020:
> Been brought up before[1] and rejected[2][3].
Anton Lindqvist on Sun, Jul 02, 2017:
> diff below in which slashes are discarded when comparing the length. I
> don't know if any other character sh
On Mon, Oct 12, 2020 at 11:20:50AM +0200, Gerhard Roth wrote:
> ix(4) relies on link-state change interrupts the update the link state
> via if_link_state_change(). However, after ixgbe_stop() all interrupts
> for the device are disabled and there won't be any IXGBE_EICR_LSC
> interrupt.
>
> Simpl
On Mon, Nov 09, 2020 at 01:10:51PM -0600, Brent Cook wrote:
>
> This updates the getentropy implementation for Windows to use the newer
> "Cryptography Next Generation APIs", replacing CryptGenRandom, which
> already has been removed from applications built for the Windows Store.
>
> Tested with
Similar to the urtwn(4) WPA1/TKIP fix I have just committed, there's
a bug in athn(4) where the value of ni_rsncipher is used to guide the
hardware- vs. software-crypto decision for multicast frames, not just
for unicast frames as was intended.
This means multicast frames could fail to decrypt if
