From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
Graham Cobb <g.btrfs@cobb.uk.net>,
linux-btrfs@vger.kernel.org
Subject: Re: Security implications of btrfs receive?
Date: Wed, 7 Sep 2016 10:55:49 -0400 [thread overview]
Message-ID: <e27b4c05-2d3c-a81a-0a54-b7f7b940feec@gmail.com> (raw)
In-Reply-To: <1473259452.24874.5.camel@scientia.net>
On 2016-09-07 10:44, Christoph Anton Mitterer wrote:
> On Wed, 2016-09-07 at 07:58 -0400, Austin S. Hemmelgarn wrote:
>> if you want proper security you should
>> be
>> using a real container system
>
> Won't these probably use the same filesystems?
That depends on how it's set up. Most container software doesn't really
care (but as this shows, they really should at least warn about this),
but has no issues running a container off of it's own filesystem, so it
ends up being an administrator decision in the end (as it arguably
should be).
next prev parent reply other threads:[~2016-09-07 14:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 9:59 Security implications of btrfs receive? Graham Cobb
2016-09-05 14:33 ` Duncan
2016-09-06 12:15 ` Austin S. Hemmelgarn
2016-09-06 17:20 ` Graham Cobb
2016-09-07 11:58 ` Austin S. Hemmelgarn
2016-09-07 14:44 ` Christoph Anton Mitterer
2016-09-07 14:55 ` Austin S. Hemmelgarn [this message]
2016-09-07 15:20 ` Austin S. Hemmelgarn
2016-09-07 16:10 ` Graham Cobb
2016-09-07 17:33 ` Austin S. Hemmelgarn
2016-09-09 16:18 ` David Sterba
2016-09-09 16:58 ` Austin S. Hemmelgarn
2016-09-07 14:41 ` Christoph Anton Mitterer
2016-09-07 15:06 ` Austin S. Hemmelgarn
2016-09-07 16:27 ` Graham Cobb
2016-09-07 18:07 ` Christoph Anton Mitterer
2016-09-07 19:08 ` Austin S. Hemmelgarn
2016-09-07 19:34 ` Chris Murphy
2016-09-08 11:48 ` Austin S. Hemmelgarn
2016-09-09 18:58 ` Chris Murphy
2016-09-10 19:27 ` Chris Murphy
2016-09-12 11:24 ` Austin S. Hemmelgarn
2016-09-12 20:25 ` Chris Murphy
2016-09-13 11:46 ` Austin S. Hemmelgarn
2016-09-09 16:33 ` David Sterba
2016-09-09 17:21 ` Austin S. Hemmelgarn
2016-09-07 20:29 ` Zygo Blaxell
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=e27b4c05-2d3c-a81a-0a54-b7f7b940feec@gmail.com \
--to=ahferroin7@gmail.com \
--cc=calestyo@scientia.net \
--cc=g.btrfs@cobb.uk.net \
--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).