This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: MoveFileW succeeding with cygwin 1.7.1 where it failed with cygwin 1.5.25?
- From: "David Byron" <dbyron at dbyron dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 8 Feb 2010 20:48:09 -0800
- Subject: RE: MoveFileW succeeding with cygwin 1.7.1 where it failed with cygwin 1.5.25?
- References: <8DC676DEED33454A9B5D962E4CB26638@pleaset>
- Reply-to: <dbyron at dbyron dot com>
On 8-feb-10 David Byron wrote:
> I've found a difference in behavior between cygwin 1.5.25
> and cygwin 1.7.1 that I don't understand. Renaming a file
> using MoveFileW fails with access denied under cygwin
> 1.5.25 as expected, but it works under 1.7.
I figured out the difference. My executable that calls MoveFileW spawned by
the version of bash I've got in my cygwin 1.7.1 installation has
SeDebugPrivilege and SeBackupPrivilege enabled. With the version of bash
I've got in my cygwin 1.5.25 installation those privileges are disabled.
When I disable the SeRestorePrivilege before calling MoveFileW, it fails
under cygwin 1.7.1 as well with access denied.
SeRestorePrivilege enabled by default
-------------------------------------
$ cygcheck -f /usr/bin/bash
bash-3.2.49-23
$ uname -r
1.7.1(0.218/5/3)
SeRestorePrivilege disabled by default
--------------------------------------
$ cygcheck -f /usr/bin/bash
bash-3.2.25-17
$ uname -r
1.5.25(0.156/4/2)
-DB
--
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