zsh-users
 help / color / mirror / code / Atom feed
From: shawn wilson <ag4ve.us@gmail.com>
To: "François Revol" <revol@free.fr>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: note metadata for files
Date: Sun, 6 Jul 2014 18:32:58 -0400	[thread overview]
Message-ID: <CAH_OBidWyhfqoE5XgarkMTc_TwWhuHHrbNsPZyU87cG2Q5Tr0w@mail.gmail.com> (raw)
In-Reply-To: <53B6870A.2050304@free.fr>

So, I'm pushing this more into the realm of OT here (ie, this no
longer has anything to do with zsh and for this reason and possibly
others, this discussion might want to go offlist)

On Fri, Jul 4, 2014 at 6:50 AM, François Revol <revol@free.fr> wrote:
> On 04/07/2014 05:55, shawn wilson wrote:

>> On Thu, Jul 3, 2014 at 5:44 PM, Peter Stephenson
>> <p.w.stephenson@ntlworld.com> wrote:
>>> On Wed, 2 Jul 2014 13:59:24 -0400
>>> shawn wilson <ag4ve.us@gmail.com> wrote:
>>>> Maybe not a zsh specific question, but...
>>>>
>>>> Does anyone have a system for attaching notes to a file?
>>>
>>> You might be interested in Oliver's article on using Linux file
>>> attributes for metadata with zsh:
>>>
>>> http://www.linux-mag.com/id/2126/
>
> As for xattrs, you'll want to check the XDG guidelines instead of
> redefining your own:
>
> http://www.freedesktop.org/wiki/CommonExtendedAttributes/
>

Heh, I had no idea there was a standard (kinda your point I guess) :)

> In case you're interested in the xattr compatibility issue, I've written
> a paper about this:
> http://dcevents.dublincore.org/IntConf/dc-2011/paper/view/53
> Sadly it seems nobody cares.

Hmmmm, so how far has your research gone here? What software ignores
xattr on which fs (how well does something like ncase deal with it)?
What security mechanisms rely on EAs and have you tried to mangle them
in order to bypass these mechanisms (either OS or application
policies)? I'd be more interested in the networked ramifications of
mangled EAs, but a copy from a thumb drive might be interesting as
well (though I doubt that would be very fruitful since moving into a
higher security realm is a bit harder in kernel space).


  reply	other threads:[~2014-07-06 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 17:59 shawn wilson
2014-07-03  7:27 ` Roman Neuhauser
2014-07-03 21:44 ` Peter Stephenson
2014-07-04  3:55   ` shawn wilson
2014-07-04 10:50     ` François Revol
2014-07-06 22:32       ` shawn wilson [this message]
2014-07-07  9:25         ` François Revol
2014-07-03 21:52 ` Mikael Magnusson

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=CAH_OBidWyhfqoE5XgarkMTc_TwWhuHHrbNsPZyU87cG2Q5Tr0w@mail.gmail.com \
    --to=ag4ve.us@gmail.com \
    --cc=revol@free.fr \
    --cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).