From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130526 invoked by alias); 10 Jul 2017 23:49:47 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 128787 invoked by uid 89); 10 Jul 2017 23:49:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*Ad:D*cs.umass.edu, H*Ad:D*umass.edu, H*f:sk:5b9b894, HTo:D*umass.edu X-HELO: mail-wr0-f170.google.com Received: from mail-wr0-f170.google.com (HELO mail-wr0-f170.google.com) (209.85.128.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Jul 2017 23:49:40 +0000 Received: by mail-wr0-f170.google.com with SMTP id k67so159262270wrc.2 for ; Mon, 10 Jul 2017 16:49:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=fdZBaglAL+zwj9+nih9fBfHHttx+lsuZBFHmLPuoJz8=; b=PbJ3+WJvm7eca4LfasqmzK9N/Mo8yRSCa1qnzHl7xmK+xVUfww3xYuXjcU5kTNo+8N tMA85ZDzoLO9JOGtUp9G3f/Q9kqeHojb12++KDL504Tfzt3FI1xPb6bIfJ93J+srwxFZ EhNX+VeTPgEY4Lr+Xtr1HBQnJ0QipTIbhbKAFeD55cy91dUk0IkpgcsM4Vv/RshirlgT IT4zYmOtpGu9ZFNzPitXAkXGHSagoRf3taKTzKZaI8ICUd5B3a5GR4fAD7AWnPfJdGCU 3UJ7PnKzlDYLzg677Rq2cEZz63aWF36+hWhGeYN8L+t/wruEZFoYiNR9W69wowGToptP 5SAA== X-Gm-Message-State: AIVw110HO1t26dvwwYUDCqm5DZVE3cnprSJtJLUON1vWL/IehQAubsuy YXrM9kfgFAJdMbkur8U5sxDsC7tFBg== X-Received: by 10.28.146.209 with SMTP id u200mr9343986wmd.38.1499730577948; Mon, 10 Jul 2017 16:49:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.144.106 with HTTP; Mon, 10 Jul 2017 16:49:36 -0700 (PDT) In-Reply-To: References: <87a84cxcos.fsf@Rainer.invalid> <64cc57cf-09c7-6225-963f-9adacb7d03af@cs.umass.edu> <5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com> From: Erik Soderquist Date: Mon, 10 Jul 2017 23:49:00 -0000 Message-ID: Subject: Re: Request to the git maintainer To: moss@cs.umass.edu, cygwin Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-07/txt/msg00159.txt.bz2 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