From: David Sterba <dsterba@suse.cz>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: better document btrfs receive security
Date: Wed, 8 Feb 2017 13:55:53 +0100 [thread overview]
Message-ID: <20170208125553.GE3366@suse.cz> (raw)
In-Reply-To: <b5e64d04-a992-afcf-55ef-e1ab0a702a71@gmail.com>
On Wed, Feb 08, 2017 at 07:29:22AM -0500, Austin S. Hemmelgarn wrote:
> On 2017-02-07 13:27, David Sterba wrote:
> > On Fri, Feb 03, 2017 at 08:48:58AM -0500, Austin S. Hemmelgarn wrote:
> >> This adds some extra documentation to the btrfs-receive manpage that
> >> explains some of the security related aspects of btrfs-receive. The
> >> first part covers the fact that the subvolume being received is writable
> >> until the receive finishes, and the second covers the current lack of
> >> sanity checking of the send stream.
> >>
> >> Signed-off-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
> >
> > Applied, thanks.
> >
> Didn't get a chance to mention this yesterday, but it looks like you
> hadn't seen the updated version I sent on the third. Message ID is:
> <20170203193805.96977-1-ahferroin7@gmail.com>
Ah sorry I missed that.
> The only significant difference is that I updated the description for
> the writablility issue using a much better description from Graham Cobb
> (with his permission of course).
>
> If you want, I can send an incremental patch on top of the original to
> update just that description.
No need to, I'll replace the patch with the latest version. Thanks.
next prev parent reply other threads:[~2017-02-08 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 13:48 [PATCH] btrfs-progs: better document btrfs receive security Austin S. Hemmelgarn
2017-02-07 18:27 ` David Sterba
2017-02-08 12:29 ` Austin S. Hemmelgarn
2017-02-08 12:55 ` David Sterba [this message]
2017-02-07 22:32 ` Kai Krakow
2017-02-07 22:40 ` Kai Krakow
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=20170208125553.GE3366@suse.cz \
--to=dsterba@suse.cz \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@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 NNTP newsgroup(s).