netdev - Re: [PATCH next] man: ss.8: add description for SCTP related entries.

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAO+A8AK1SeBnB5DDq+HPXiMHRreUgHs-f4LE=LkkWp2jz5zPcg@mail.gmail.com>
Date: Tue, 3 Dec 2024 08:21:18 +0530
From: Abhishek Rawal <rawal.abhishek92@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, dsahern@...il.com, arawal@...hat.com, 
	jamie.bainbridge@...il.com
Subject: Re: [PATCH next] man: ss.8: add description for SCTP related entries.

> It is good to have more entries documented, but throwing entries
> into the "some of the following" list just adds to an already messy section.

Okay, I agree. Thank you for the feedback.

I think of two implementation ideas for v2 :
a] Create headings per protocol under --info.
b] Update entire --info section for different protocols & its
descriptions. Similar to : STATE-FILTER.

May I have your opinion please ? Do you have any other implementation ideas ?

On Tue, 3 Dec 2024 at 00:59, Stephen Hemminger
<stephen@...workplumber.org> wrote:
>
> On Thu, 28 Nov 2024 10:13:40 +0530
> rawal.abhishek92@...il.com wrote:
>
> > From: Abhishek Rawal <rawal.abhishek92@...il.com>
> >
> > SCTP protocol support is included, but manpage lacks
> > the description for its entries. Add the missing
> > descriptions so that SCTP information is complete.
> >
> > Signed-off-by: Abhishek Rawal <rawal.abhishek92@...il.com>
> > Reviewed-by: Jamie Bainbridge <jamie.bainbridge@...il.com>
>
> It is good to have more entries documented, but throwing entries
> into the "some of the following" list just adds to an already messy section.
>
> Similar issue is true for mptcp fields.