From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: A notion about saving and restoring Windows file security info
Date: Wed, 5 Jan 2022 11:34:16 +0100 [thread overview]
Message-ID: <YdV0KNw+hZ5iS1AC@calimero.vinschen.de> (raw)
In-Reply-To: <4c5fda33-8f7e-53d2-85ce-28eb11cfb978@cs.umass.edu>
On Jan 4 22:45, Eliot Moss wrote:
> Dear Cygwiners - Maybe this idea has been discussed before, and I can't say I
> exactly have a specific application in mind, but I was wondering about how one
> might achieve reliable backup/restore of files on a Windows system via a
> backup program written to the POSIX interface and ported to Windows via
> Cygwin.
>
> The idea is this: expose the Windows file attributes (such as system, archive,
> hidden, etc.) as well as security descriptors (such as managed by icacls), via
> specifically named extended attributes, those read/written by get/setfattr.
> The Cygwin library could be enhanced to "know" the special names of these
> attributes and use the appropriate, different, underlying calls to get/set
> them.
>
> Is this a crazy idea? A useful one? (How useful?) What implementation
> effort would be required?
It would be possible with not too much effort. That would need a bit
of discussion, for instance, do we want to show up the native ACL in
listxattr?
Corinna
next prev parent reply other threads:[~2022-01-05 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 3:45 Eliot Moss
2022-01-05 10:34 ` Corinna Vinschen [this message]
2022-01-05 17:41 ` Eliot Moss
2022-01-06 9:03 ` Sam Edge
2022-01-07 13:02 ` Corinna Vinschen
2022-01-07 14:28 ` Eliot Moss
2022-01-07 14:53 ` Corinna Vinschen
2022-01-07 15:40 ` Andrey Repin
2022-01-10 9:59 ` Corinna Vinschen
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=YdV0KNw+hZ5iS1AC@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).