netdev - Re: syslog spam: TCP segment has incorrect auth options set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <491b1b19-f719-1aa6-7757-ba4168228bbd@nerdbynature.de>
Date: Thu, 4 Jan 2024 17:03:57 +0100 (CET)
From: Christian Kujau <lists@...dbynature.de>
To: Dmitry Safonov <dima@...sta.com>
cc: netdev@...r.kernel.org, Dmitry Safonov <0x7f454c46@...il.com>, 
    Francesco Ruggeri <fruggeri@...sta.com>, 
    Salam Noureddine <noureddine@...sta.com>, David Ahern <dsahern@...nel.org>, 
    linux-kernel@...r.kernel.org
Subject: Re: syslog spam: TCP segment has incorrect auth options set

On Thu, 4 Jan 2024, Dmitry Safonov wrote:
> Yeah, I guess it's possible to down the severity of these logs, but may
> be unexpected by admins: TCP-MD5 messages existed for long time and
> there may be userspace that expects them (i.e. in arista there are tests
> that look for these specific messages - those would be easy to fix, but
> there may be others outside this company).

Understood, thanks for explaining that.

> While thinking on the origin of your issue, it seems that the logs
> produced by either TCP-MD5 or TCP-AO are desired by a user when they
> add/use the authentication. Could you try this and see if that solves
> the issue for you?

Thanks for preparing that patch so quickly, did not expect that :-)

I've applied this on top of 6.7.0-rc8 and will report back if I see those 
messages again in the next days.

Thank you!
Christian.
-- 
BOFH excuse #127:

Sticky bits on disk.