KernelCI discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Arisu Tachibana <arisu.tachibana@miraclelinux.com>
Cc: Gustavo Padovan <gustavo.padovan@collabora.com>,
	kernelci <kernelci@lists.linux.dev>
Subject: Re: CRA compliance
Date: Thu, 9 Oct 2025 16:12:34 +0200	[thread overview]
Message-ID: <2025100938-coronary-bronco-8a2b@gregkh> (raw)
In-Reply-To: <CANgtXuNUm=5pyYwQ_Z1EfK_7oKkU7a-VhUkw8h_1Xg9=j8OVXg@mail.gmail.com>

On Thu, Oct 09, 2025 at 10:58:18PM +0900, Arisu Tachibana wrote:
> On Thu, Oct 9, 2025 at 10:06 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > > Then for security breaches in KernelCI, it would be a best practice to create kernelci-security@
> > > mailing list for people to report issues and for us to community privately with parties running
> > > KernelCI infra too.
> >
> > "communicate privately" == "private communication channels" which opens
> > up a TON of legal issues, as I am want to talk at length with :)
> >
> > Be VERY VERY VERY careful with this, there's a whole boatload of
> > problems that you can get into when doing this as you are taking a
> > public project's communications private to specific companies/entities.
> >
> > Anyway, having a security@ address is great to REPORT bugs to, but
> > please refrain from using that to attempt to coordinate security fix
> > rollouts.  That way lies a death by a thousand paper cuts and
> > potentially talking to government entities when you least expect it.
> >
> > I can go into much more detail if people really want.
> >
> 
> Would be nice to have more detail on this topic in the future.

See my 2023 Kernel Recipies talk:
	https://www.youtube.com/watch?v=2TZe5EROFhE
around the 22:30 minute mark for more details.

thanks,

greg k-h

  reply	other threads:[~2025-10-09 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 10:43 CRA compliance Arisu Tachibana
2025-10-09 10:48 ` Greg KH
2025-10-09 12:51   ` Gustavo Padovan
2025-10-09 13:06     ` Greg KH
2025-10-09 13:58       ` Arisu Tachibana
2025-10-09 14:12         ` Greg KH [this message]
2025-10-09 17:56       ` Gustavo Padovan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025100938-coronary-bronco-8a2b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arisu.tachibana@miraclelinux.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=kernelci@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox