From: Eliot Moss <moss@cs.umass.edu>
To: cygwin <cygwin@cygwin.com>
Subject: A notion about saving and restoring Windows file security info
Date: Tue, 4 Jan 2022 22:45:29 -0500 [thread overview]
Message-ID: <4c5fda33-8f7e-53d2-85ce-28eb11cfb978@cs.umass.edu> (raw)
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?
What brought it to mind is the restic backup/restore program, which AFAIK
lacks support for these things, but does know how to save/restore xattrs. (So
I could fake the same thing there, provided I duplicate in golang in restic
what I am suggesting might be done for Cygwin in it library.)
Regards - Eliot
next reply other threads:[~2022-01-05 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 3:45 Eliot Moss [this message]
2022-01-05 10:34 ` Corinna Vinschen
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=4c5fda33-8f7e-53d2-85ce-28eb11cfb978@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).