From: Jonathan Bar Or <jonathanbaror@gmail.com>
To: barebox@lists.infradead.org
Subject: Reporting security issues preferred method?
Date: Sun, 9 Feb 2025 18:39:14 -0800 [thread overview]
Message-ID: <CABMsoEEwH4Nch6bVqd+8QSMOCzMTN9LVZcSe6yJ=+Rf54sAVDg@mail.gmail.com> (raw)
Hi Barebox mailing list!
What's the best way to report security issues?
Best regards,
Jonathan
next reply other threads:[~2025-02-10 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 2:39 Jonathan Bar Or [this message]
2025-02-10 9:03 ` Sascha Hauer
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='CABMsoEEwH4Nch6bVqd+8QSMOCzMTN9LVZcSe6yJ=+Rf54sAVDg@mail.gmail.com' \
--to=jonathanbaror@gmail.com \
--cc=barebox@lists.infradead.org \
/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