From: David Disseldorp <ddiss@suse.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: [PATCH] make-release-tarball.sh: run cargo audit
Date: Fri, 8 Mar 2024 14:59:26 +1100 [thread overview]
Message-ID: <20240308145926.0b7f7ef6@echidna> (raw)
In-Reply-To: <n6p6xwwrm4rusf2wjrhqromfajixigo5ddc3ma46ch3f3w7jhi@mwl3h25abthd>
On Thu, 7 Mar 2024 21:16:02 -0500, Kent Overstreet wrote:
> On Tue, Jan 30, 2024 at 06:03:56PM +1100, David Disseldorp wrote:
> > cargo audit can be used to check bcachefs dependencies for
> > vulnerabilities published in the advisory database at
> > https://github.com/RustSec/advisory-db.git
> >
> > Given the significant size of dependency sources (currently ~292M),
> > manual audit is mostly unviable, so rely on this for now.
>
> Not a good place for this, workflow-wise; I run make-release-tarball.sh
> after the new release is tagged and frequently after the tag is
> uploaded.
>
> This would better be run as some sort of cron job that emails results to
> the list when something is found.
Fair enough, will set something up as part of the downstream (openSUSE)
release process.
prev parent reply other threads:[~2024-03-08 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:03 [PATCH] make-release-tarball.sh: run cargo audit David Disseldorp
2024-03-05 0:49 ` David Disseldorp
2024-03-08 2:16 ` Kent Overstreet
2024-03-08 3:59 ` David Disseldorp [this message]
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=20240308145926.0b7f7ef6@echidna \
--to=ddiss@suse.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).