public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Erik Soderquist <ErikSoderquist@gmail.com>
To: moss@cs.umass.edu, cygwin <cygwin@cygwin.com>
Subject: Re: Request to the git maintainer
Date: Mon, 10 Jul 2017 23:49:00 -0000	[thread overview]
Message-ID: <CACoZoo1=EOPqL4h0t6fYkP2pcWedXHtALqUoM9TCmRGi_u7Odw@mail.gmail.com> (raw)
In-Reply-To: <aa3bdabb-5e98-ada9-f033-15b675dee069@cs.umass.edu>

On Mon, Jul 10, 2017 at 7:17 PM, Eliot Moss  wrote:
> I'm not asking "every vendor".  I'm asking a limited number of
> cygwin port maintainers (and so far only one specifically).
>
> CrashPlan does not have "bizarre" limitations -- it quite
> naturally has some difficulty if a file's access does not grant
> it permission.

In my experience, that is a bizarre limitation; I have yet to work
with a Windows backup program that does not have the ability to bypass
permissions when performing a backup or restore when it has been
properly configured.  Even simple robocopy has this option.

> The permissions on these files is what is bizarre.  There is no
> good reason they should deny read access.

I work with a lot of customers where the opposite perspective is taken
for security and confidentiality reasons -- if you don't have a very
strong reason to allow access, you deny by default.

> Windows does not really have an equivalent of "root" that can
> access anything, so there is not really any privilege I can
> give the backup tool that is guaranteed to work in all cases.

Windows does have its backup operators set of permissions, allowing
the backup processes to archive and restore files the user would not
normally have access to without changing those permissions and even
with restoring the permissions as they were archived.  I would check
with the CrashPlan admins for why they are not using the backup
operators permissions.

> I can fix the access mode manually, but every time there is an
> update to the package, it will revert, so that's not a great
> solution.

You should not have to change the file permissions, regardless of what
they are; Windows based backup software should not be having a problem
with the existing permissions.

-- Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-07-10 23:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 18:23 Eliot Moss
2017-07-10 20:24 ` Achim Gratz
2017-07-10 20:45   ` Eliot Moss
2017-07-10 21:02   ` Eliot Moss
2017-07-10 22:27     ` Kaz Kylheku
2017-07-10 23:17       ` Eliot Moss
2017-07-10 23:49         ` Erik Soderquist [this message]
2017-07-11  1:38         ` Brian Inglis
2017-07-11  2:00           ` Eliot Moss
2017-07-11  2:33             ` Brian Inglis
2017-07-11 12:34               ` Eliot Moss
2017-07-11 16:34                 ` Eliot Moss
2017-07-11 20:35     ` Achim Gratz

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='CACoZoo1=EOPqL4h0t6fYkP2pcWedXHtALqUoM9TCmRGi_u7Odw@mail.gmail.com' \
    --to=eriksoderquist@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=moss@cs.umass.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 read-only IMAP folder(s) and NNTP newsgroup(s).