linux-hardening.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Tycho Andersen <tycho@tycho.pizza>
Cc: Kees Cook <keescook@chromium.org>,
	"Tobin C. Harding" <me@tobin.cc>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Guixiong Wei <guixiongwei@gmail.com>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/4] leaking_addresses: Provide mechanism to scan binary files
Date: Thu, 22 Feb 2024 14:00:47 -0800	[thread overview]
Message-ID: <20240222215755.it.764-kees@kernel.org> (raw)

Hi,

Since I was in this script for the binary file scanning, I did other
clean-ups and tweaked the MAINTAINERS file per Tycho's suggestion.

Changes in v2: patches 1-3, move hex() after ^0 skip
Prior v1: https://lore.kernel.org/linux-hardening/20240218173809.work.286-kees@kernel.org/

-Kees

Kees Cook (4):
  MAINTAINERS: Update LEAKING_ADDRESSES details
  leaking_addresses: Use File::Temp for /tmp files
  leaking_addresses: Ignore input device status lines
  leaking_addresses: Provide mechanism to scan binary files

 MAINTAINERS                  |  4 +-
 scripts/leaking_addresses.pl | 90 +++++++++++++++++++++++++++++-------
 2 files changed, 76 insertions(+), 18 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-02-22 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 22:00 Kees Cook [this message]
2024-02-22 22:00 ` [PATCH v2 1/4] MAINTAINERS: Update LEAKING_ADDRESSES details Kees Cook
2024-02-22 22:00 ` [PATCH v2 2/4] leaking_addresses: Use File::Temp for /tmp files Kees Cook
2024-02-22 22:00 ` [PATCH v2 3/4] leaking_addresses: Ignore input device status lines Kees Cook
2024-02-22 22:00 ` [PATCH v2 4/4] leaking_addresses: Provide mechanism to scan binary files Kees Cook
2024-02-22 23:55 ` [PATCH v2 0/4] " Tycho Andersen

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=20240222215755.it.764-kees@kernel.org \
    --to=keescook@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=guixiongwei@gmail.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=tycho@tycho.pizza \
    /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;
as well as URLs for NNTP newsgroup(s).