linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Richard Sharpe <realrichardsharpe@gmail.com>,
	Richard Yao <ryao@gentoo.org>,
	Cedric Blancher <cedric.blancher@gmail.com>,
	Theodore Ts'o <tytso@mit.edu>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Steve French <smfrench@gmail.com>
Subject: Re: Making an interface for alternative data streams
Date: Tue, 22 Mar 2016 14:42:55 -0700	[thread overview]
Message-ID: <20160322214255.GA10921@jra3> (raw)
In-Reply-To: <20160322200801.GF4083@fieldses.org>

On Tue, Mar 22, 2016 at 04:08:01PM -0400, J. Bruce Fields wrote:
> 
> But you do see people using "named attributes"/"alternative data
> streams"?
> 
> This comes up at the LSF/MM summit every now and then and Jeremy Allison
> inevitably says "hah, only malware writers use those", and that's the
> end of the discussion.  Sounds like Richard Yao has heard otherwise, but
> it'd be nice to have actual examples of users.

The only use I know of other than malware writers is
the :Zone.Identifier stream used by Internet Explorer.

http://woshub.com/how-windows-determines-that-the-file-has-been-downloaded-from-the-internet/

Not sure if the new Microsoft browser still uses them
(I haven't used desktop Windows in over 10 years).

  parent reply	other threads:[~2016-03-22 21:43 UTC|newest]

Thread overview: 26+ 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
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 [this message]
2016-03-23  4:13                     ` Steve French
2016-03-23  4:19                       ` Steve French
2016-03-23 14:45                         ` Steve French
     [not found]                           ` <CAH2r5muya2+hWQup99QcxKV9XE4T_pWW565+fqWeu1tAnXSxoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=20160322214255.GA10921@jra3 \
    --to=jra@samba.org \
    --cc=bfields@fieldses.org \
    --cc=cedric.blancher@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=realrichardsharpe@gmail.com \
    --cc=ryao@gentoo.org \
    --cc=smfrench@gmail.com \
    --cc=tytso@mit.edu \
    /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).