linux-kernel - Re: [PATCH 4/4] agents: add legal requirements and agent attribution guidelines

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: <20250806-impetuous-rainbow-octopus-2dcaab@lemur>
Date: Wed, 6 Aug 2025 10:12:59 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Sasha Levin <sashal@...nel.org>
Cc: corbet@....net, linux-doc@...r.kernel.org, workflows@...r.kernel.org, 
	josh@...htriplett.org, kees@...nel.org, linux-kernel@...r.kernel.org, 
	rostedt@...dmis.org
Subject: Re: [PATCH 4/4] agents: add legal requirements and agent attribution
 guidelines

On Sun, Jul 27, 2025 at 03:58:02PM -0400, Sasha Levin wrote:
> +- ``Co-developed-by: Claude claude-3-opus-20240229``
> +- ``Co-developed-by: GitHub-Copilot GPT-4 v1.0.0``
> +- ``Co-developed-by: Cursor gpt-4-turbo-2024-04-09``

FYI, this will break tools that expect Co-developed-by: to be in the address
header format. I will add exceptions in b4, but it *is* going to be annoying
that this trailer can be in both formats and I expect other tooling will also
have similar problems.

If it's not too late, I recommend picking a wholly new trailer instead of
overloading Co-developed-by. Examples:

    | Assisted-by: Claude claude-3-opus-20240229
    | Auxiliary-tooling: GitHub-Copilot GPT-4 v1.0.0

I like the latter, because this also allows listing multiple tools.

-K