Re: iwm(4): fix ccmp decrypt edge cases

2019-08-15 Thread Stefan Sperling
On Thu, Aug 15, 2019 at 03:47:02PM +1200, richard.n.proc...@gmail.com wrote: > On Thu, 15 Aug 2019, richard.n.proc...@gmail.com wrote: > > > On Tue, Aug 13, 2019 at 10:47:24AM -0300, Martin Pieuchot wrote: > > > > if the crash is because of a missing key, put one :) > > > > > > Yes, you've convinc

nmea 4.1

2019-08-15 Thread Otto Moerbeek
Hi, NMEA 4.1 appends an extra field to the RMC message. We're not interested in it's value, but we do want to accept the new format. Tested to work on a nav module enabled for Galileo info (which requires NMEA 4.1). OK? -Otto Index: tty_nmea.c ==

Re: nmea 4.1

2019-08-15 Thread Mark Kettenis
> Date: Thu, 15 Aug 2019 13:32:37 +0200 > From: Otto Moerbeek > > Hi, > > NMEA 4.1 appends an extra field to the RMC message. We're not > interested in it's value, but we do want to accept the new format. > > Tested to work on a nav module enabled for Galileo info (which > requires NMEA 4.1). >

ssh_config.5: Clarify Ciphers and KexAlgorithms semantics

2019-08-15 Thread Klemens Nanni
The current wording explaining how to append or exclude ciphers seems ambiguous as to whether an optional dash or plus character is to be prepended once to the entire list or every cipher in the list. Diff below slightly tweaks it without substantial changes, making it clearer (at least for non-na

Re: ssh_config.5: Clarify Ciphers and KexAlgorithms semantics

2019-08-15 Thread Jason McIntyre
On Thu, Aug 15, 2019 at 06:44:24PM +0200, Klemens Nanni wrote: > The current wording explaining how to append or exclude ciphers seems > ambiguous as to whether an optional dash or plus character is to be > prepended once to the entire list or every cipher in the list. > > Diff below slightly twea

Re: ssh_config.5: Clarify Ciphers and KexAlgorithms semantics

2019-08-15 Thread Klemens Nanni
On Thu, Aug 15, 2019 at 06:50:38PM +0100, Jason McIntyre wrote: > try as i can, i can;t really see how this wording avoids the ambiguity. > nor how the current wording contains it exactly. s/then the/all/ is an attempt at making it clearer the prefix effects not just the immediately following ciphe

Re: ssh_config.5: Clarify Ciphers and KexAlgorithms semantics

2019-08-15 Thread Klemens Nanni
On Thu, Aug 15, 2019 at 06:50:38PM +0100, Jason McIntyre wrote: > what about > > If the cipher list begins with a > .Sq > character ... Here's a diff that does s/value/list/ for all options mentioning "ssh -Q ...": since this part already says "list", it seems quite nice.

Re: ssh_config.5: Clarify Ciphers and KexAlgorithms semantics

2019-08-15 Thread Jason McIntyre
On Thu, Aug 15, 2019 at 10:57:38PM +0200, Klemens Nanni wrote: > On Thu, Aug 15, 2019 at 06:50:38PM +0100, Jason McIntyre wrote: > > what about > > > > If the cipher list begins with a > > .Sq > > character ... > Here's a diff that does s/value/list/ for all options mentioning > "ssh -

pf congestion on low traffic

2019-08-15 Thread Eric Camirand
Hello, I'm testing new servers (same mboard/cpu) and getting 'congestion' in the pf information output on very low level of traffic (~100 pps). Traffic is coming in on em0:901 and em0:2906 using carp. Traffic level is monitored on the switch port. First tried 6.5-stable and now using 6.6-beta.