X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 31 Mar 2008 13:41:29 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: using Windows backup API? Message-ID: <20080331114129.GA28726@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <47F0B0EC DOT 5000702 AT wpkg DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47F0B0EC.5000702@wpkg.org> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 31 11:37, Tomasz Chmielewski wrote: > Traditionally, in UNIX, a root user can access any file in the system > without doing anything special. > > This contrasts with Windows, where even Administrator user can't read files > for which he has not access permissions (i.e., a file with all permissions > removed)[1]. > > To access such files in Windows, one needs to use a special Backup API. The backup API is not really necessary to access such files. It's enough to enable the SE_BACKUP_NAME privilege and to use the FILE_OPEN_FOR_BACKUP_INTENT flag in file and directory open calls. This is partly already done in the current Cygwin release, but it will only be done consequently in the next major release 1.7.0. No, we don't have a release date yet. Feel free to test the latest Cygwin snapshots from http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/