netdev - Re: [devel-ipsec] [RFC ipsec-next v2 0/8] Add IP-TFS mode to xfrm

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <m21qck1cxz.fsf@ja.int.chopps.org>
Date: Mon, 20 Nov 2023 13:39:50 -0500
From: Christian Hopps <chopps@...n.net>
To: Andrew Cagney <andrew.cagney@...il.com>
Cc: Steffen Klassert <steffen.klassert@...unet.com>, Christian Hopps
 <chopps@...pps.org>, devel@...ux-ipsec.org, netdev@...r.kernel.org,
 Christian Hopps <chopps@...n.net>
Subject: Re: [devel-ipsec] [RFC ipsec-next v2 0/8] Add IP-TFS mode to xfrm


Andrew Cagney <andrew.cagney@...il.com> writes:

>> I did a multiple days peer review with Chris on this pachset. So my
>> concerns are already addressed.
>>
>> Further reviews are welcome! This is a bigger change and it would
>> be nice if more people could look at it.
>
> I have a usability question.  What name should appear when a user
> interacts with and sees log messages from this feature?
>     ip-tfs, IP-TFS, IP_TFS
> or:
>    iptfs, IPTFS, ...

I think no `-` or `_` in the code/api. For documentation it is probably better to hew closer to the RFC and use `IP-TFS`.

Thanks,
Chris.

Download attachment "signature.asc" of type "application/pgp-signature" (859 bytes)