From: "Theodore Ts'o" <tytso@mit.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Richard Yao <ryao@gentoo.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Making an interface for alternative data streams
Date: Mon, 21 Mar 2016 18:36:27 -0400 [thread overview]
Message-ID: <20160321223627.GA12999@thunk.org> (raw)
In-Reply-To: <20160321204041.GA807@fieldses.org>
On Mon, Mar 21, 2016 at 04:40:41PM -0400, J. Bruce Fields wrote:
> On Mon, Mar 21, 2016 at 04:19:17PM -0400, Richard Yao wrote:
> > Maybe I should clarify that the idea is to allow read/write/list of
> > extended attributes via read/write/readdir so that those that want
> > extended attributes that are alternative data streams can have them. I
> > do not want to see extended attributes and alternative data streams be
> > different things.
>
> I think there are differences between the two that make this awkward.
> Does anyone actually use alternative data stream for anything that makes
> the effort worthwhile?
Windows malware authors *love* to use alternate data streams as a
place to hide their malware where many security scanners weren't
looking, and certainly most users won't find.
Does that count? :-)
- Ted
next prev parent reply other threads:[~2016-03-21 22:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 18:11 Making an interface for alternative data streams Richard Yao
2016-03-21 18:18 ` Christoph Hellwig
2016-03-21 18:51 ` Richard Yao
2016-03-21 19:17 ` Richard Yao
2016-03-21 20:19 ` Richard Yao
2016-03-21 20:40 ` J. Bruce Fields
2016-03-21 22:36 ` Theodore Ts'o [this message]
2016-03-21 22:48 ` Cedric Blancher
2016-03-22 0:12 ` J. Bruce Fields
2016-03-22 1:02 ` Richard Yao
2016-03-22 2:21 ` Richard Yao
2016-03-22 16:15 ` Richard Sharpe
2016-03-22 20:08 ` J. Bruce Fields
2016-03-22 20:13 ` Richard Sharpe
2016-03-22 20:32 ` J. Bruce Fields
2016-03-22 21:42 ` Jeremy Allison
2016-03-23 4:13 ` Steve French
2016-03-23 4:19 ` Steve French
2016-03-23 14:45 ` Steve French
2016-03-23 17:01 ` Jeremy Allison
2016-03-23 17:01 ` Jeremy Allison
2016-03-23 17:16 ` Steve French
2016-03-23 15:16 ` J. Bruce Fields
2016-03-22 2:01 ` Richard Yao
2016-03-22 21:29 ` Dave Chinner
2016-03-22 21:52 ` J. Bruce Fields
2016-03-22 22:50 ` Dave Chinner
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=20160321223627.GA12999@thunk.org \
--to=tytso@mit.edu \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ryao@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.