public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Re: cygwin permissions problem on a network drive
@ 2011-10-18 12:52 Lemke, Michael  SZ/HZA-ZSW
  2011-10-20 22:58 ` gds
  0 siblings, 1 reply; 21+ messages in thread
From: Lemke, Michael  SZ/HZA-ZSW @ 2011-10-18 12:52 UTC (permalink / raw)
  To: cygwin

On Jul  5 10:59, Corinna Vinschen wrote:
>On Jul  5 12:21, Bill Metzenthen wrote:
>> I have problems with permissions on a network drive.  The drive is
>> maintained by others and I have no control over the Windows
>> permissions of the drive.
>> [...]
>> If I now try to use cygwin to create anything then it fails (despite
>> it reporting that I have rwx permissions for the directory):
>
>For now, set the mount point for this drive to "noacl".  If you're
>accessing the share via /cygdrive, create a distinct mount point for it.
>
>I know what change in Cygwin is causing that problem, but unfortunately
>I could never reproduce the server share settings myself which result in
>the permission denied.

I know this an old thread but I am in exactly the same situation as
the OP.  Access with 1.7.7 and before worked fine, 1.7.9 has this
problem.  The workaround with explicit noacl option works for me but
it is rather awkward as I have to work with a lot of servers.

So...

>...
>
>If you want to discuss this with your admin, the problem is this:  When
>Cygwin 1.7.9 tries to create a file on a filesystem which supports ACLs,
>it requests WRITE_DAC permissions in the open call.  WRITE_DAC is the
>access right you need to create the permission bits in the file's ACL,
>what you see in Explorer under the Security tab.
>
>Now, in some environments, the settings of the shares are so, that this
>right is apparently not granted, even for the creator of the file.
>But, as far as earlier reports go, there seem to be no indication of
>this in the ACL.  As I mentioned above, I experimented with this
>myself, but I have never managed to reproduce this setting on the server.
>So I neither know how this setting looks like, nor if there's a way
>to recognize such a share.
>
>So, for the time being, I will change this in Cygwin for the next
>version so that it doesn't request WRITE_DAC permissions when trying
>to create a file or directory on a network share.

...has this happened now?  In a snapshot?  I couldn't find any
further information.


Thanks,
Michael


--
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

^ permalink raw reply	[flat|nested] 21+ messages in thread
* Re: cygwin permissions problem on a network drive
@ 2012-01-04 14:25 Markus Leuthold
  2012-01-09 13:52 ` Corinna Vinschen
  0 siblings, 1 reply; 21+ messages in thread
From: Markus Leuthold @ 2012-01-04 14:25 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2032 bytes --]

On Jul  5 10:59, Corinna Vinschen wrote:
> On Jul  5 12:21, Bill Metzenthen wrote:
> > What should I ask the system administrator to change so that cygwin
> > will once again work on this drive? Perhaps there is some new setting
> > (or an old one which has somehow changed) for cygwin that I have
> > failed to notice?
>
> If you want to discuss this with your admin, the problem is this:  When
> Cygwin 1.7.9 tries to create a file on a filesystem which supports ACLs,
> it requests WRITE_DAC permissions in the open call.  WRITE_DAC is the
> access right you need to create the permission bits in the file's ACL,
> what you see in Explorer under the Security tab.
>
> Now, in some environments, the settings of the shares are so, that this
> right is apparently not granted, even for the creator of the file.
> But, as far as earlier reports go, there seem to be no indication of
> this in the ACL.  As I mentioned above, I experimented with this
> myself, but I have never managed to reproduce this setting on the 
server.
> So I neither know how this setting looks like, nor if there's a way
> to recognize such a share.
>
>Btw, if you're going to discuss this with your admin, and if you figure
>out what server setting is the culprit, I would be glad if you could
>share the information with us.  It might be a great help in developing
>Cygwin further.
>
>
>Thanks,
>Corinna


Hello Corinna

I've run into the same problem on a DFS filesystem, and I asked our 
admins about the settings. Please find a screenshot here: 
http://titlis.org/serversettings.png

The reason why "change permission" (=WRITE_DAC) was disabled: Our admins 
don't want to allow "take ownership" to everybody, since in the past users 
managed to set the rights such that even the admins couldn't access the 
file anymore. Since "take ownership" automatically enables "change 
permissions", WRITE_DAC is thus disabled too.

hope that helps

best regards, Kusi

PS: your workaround works fine, too




[-- Attachment #2: Type: text/plain, Size: 218 bytes --]

--
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

^ permalink raw reply	[flat|nested] 21+ messages in thread
* Re: cygwin permissions problem on a network drive
@ 2011-08-02 16:10 spambouncer
  2011-08-02 20:54 ` Larry Hall (Cygwin)
  0 siblings, 1 reply; 21+ messages in thread
From: spambouncer @ 2011-08-02 16:10 UTC (permalink / raw)
  To: cygwin

> On Jul  6 11:43, Bill Metzenthen wrote:
> > Corinna Vinschen wrote:
> > >> If I now try to use cygwin to create anything then it fails (despite
> > >> it reporting that I have rwx permissions for the directory):
> > >
> > > For now, set the mount point for this drive to "noacl".  If you're
> > > accessing the share via /cygdrive, create a distinct mount point for it.
> > 
> > I'm not sure that I'm doing this the right way.
> 
> No.  I meant a distinct mount point, *different* from your cygdrive
> prefix.  See http://cygwin.com/cygwin-ug-net/using.html#cygdrive
> 
> This works:
> 
>   H: /h xyz binary,noacl 0 0 
>   none /mnt cygdrive binary,posix=0,user 0 0
> 
> Or this:
> 
>   H: /myhome xyz binary,noacl 0 0 
>   none / cygdrive binary,posix=0,user 0 0
> 
> Corinna


I'm having the same problems with my $HOME folder, which is on a network share. I was able to create an extra mount point for the location, unfortunately that didn't help with the original $HOME. Could you please describe what I have to do circumvent the permission problem for $HOME?

Thanks a lot,
Spam Bouncer



-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren: http://www.gmx.net/de/go/freephone

--
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

^ permalink raw reply	[flat|nested] 21+ messages in thread
* Re: cygwin permissions problem on a network drive
@ 2011-07-06  1:43 Bill Metzenthen
  2011-07-06  6:31 ` Corinna Vinschen
  0 siblings, 1 reply; 21+ messages in thread
From: Bill Metzenthen @ 2011-07-06  1:43 UTC (permalink / raw)
  To: cygwin

Corinna Vinschen wrote:
>> If I now try to use cygwin to create anything then it fails (despite
>> it reporting that I have rwx permissions for the directory):
>
> For now, set the mount point for this drive to "noacl".  If you're
> accessing the share via /cygdrive, create a distinct mount point for it.

I'm not sure that I'm doing this the right way.

I created an entry in /etc/fstab and then I got:
$ mount
C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin on / type ntfs (binary,auto)
H: on /h type ntfs (binary,noacl,posix=0,user)
C: on /c type ntfs (binary,posix=0,user,noumount,auto)

Unfortunately, this didn't fix my problem.

So then for some reason I don't remember, I commented out the
following line from /etc/fstab:
none / cygdrive binary,posix=0,user 0 0

This resulted in my being able to create directories and files on the
network drive.  It came at a cost however because C: was now mounted
on /cydrive/c, so I added and explicit entry for the C: drive in
/etc/fstab and this appears to have fixed the problem:
$ mount
C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/cygwin on / type ntfs (binary,auto)
C: on /c type ntfs (binary,posix=0,user)
H: on /h type ntfs (binary,noacl,posix=0,user)

This has the minor problem that it allows me to get into a mess by umounting /c

--
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

^ permalink raw reply	[flat|nested] 21+ messages in thread
* cygwin permissions problem on a network drive
@ 2011-07-05  2:21 Bill Metzenthen
  2011-07-05  8:59 ` Corinna Vinschen
  0 siblings, 1 reply; 21+ messages in thread
From: Bill Metzenthen @ 2011-07-05  2:21 UTC (permalink / raw)
  To: cygwin

I have problems with permissions on a network drive.  The drive is
maintained by others and I have no control over the Windows
permissions of the drive.

I have a directory on the drive and I can use Windows Explorer to
create and write files and subdirectories to it.  I can also use the
Windows 'mkdir' and 'copy' commands to create directories and write
files on the drive.

Until recently I could do the same things from cygwin.  But that has changed...

If I cd in cygwin to a empty subdirectory I have created on the drive
then I find:

$ ls -la
total 0
drwx------+ 1 bmetzenthen Domain Users 0 Jul  4 11:51 .
drwx------+ 1 bmetzenthen Domain Users 0 Jul  4 11:52 ..

Where 'bmetzenthen' is me:

$ whoami
bmetzenthen

If I now try to use cygwin to create anything then it fails (despite
it reporting that I have rwx permissions for the directory):

$ mkdir test
mkdir: cannot create directory `test': Permission denied

Similarly for 'touch':

$ touch test
touch: cannot touch `test': Permission denied

If a subdirectory (or a file) is created by Windows Explorer then
'rmdir test' works.  Similarly 'touch test' and 'mv test test2'.

Windows Explorer reports that the subdirectories (but not files) are
read-only but silently fails to remove its read-only flag if I try
that.  It reports that I have all permissions but not 'Full Control'.

My cygwin installation is up to date and cygcheck -c reports all packages as OK.

What should I ask the system administrator to change so that cygwin
will once again work on this drive?  Perhaps there is some new setting
(or an old one which has somehow changed) for cygwin that I have
failed to notice?

Bill Metzenthen

--
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

^ permalink raw reply	[flat|nested] 21+ messages in thread
end of thread, other threads:[~2012-01-09 13:52 UTC | newest]

Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-10-18 12:52 cygwin permissions problem on a network drive Lemke, Michael  SZ/HZA-ZSW
2011-10-20 22:58 ` gds
2011-10-21  8:50   ` Corinna Vinschen
2011-10-21 10:16     ` Lemke, Michael  SZ/HZA-ZSW
2011-10-21 10:55       ` Corinna Vinschen
2011-10-21 14:14         ` Lemke, Michael  SZ/HZA-ZSW
2011-10-21 14:37           ` Corinna Vinschen
2011-10-21 15:11             ` Lemke, Michael  SZ/HZA-ZSW
2011-10-21 14:17         ` gds
2011-10-21 14:39           ` Corinna Vinschen
2011-10-21 16:32             ` gds
2011-10-21 17:34               ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2012-01-04 14:25 Markus Leuthold
2012-01-09 13:52 ` Corinna Vinschen
2011-08-02 16:10 spambouncer
2011-08-02 20:54 ` Larry Hall (Cygwin)
2011-07-06  1:43 Bill Metzenthen
2011-07-06  6:31 ` Corinna Vinschen
2011-07-05  2:21 Bill Metzenthen
2011-07-05  8:59 ` Corinna Vinschen
2011-07-05  9:13   ` Corinna Vinschen

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).