Re[2]: Issues with ACL settings after updating to the latest cygwin.dll
Which warning do you mean here?
The "permissions out of order" one. This was not the case before, at
least not on my installation, so I don't see how this can be called
normal.
Come on, be fair. The new ACL handling started out early 2015, got a
break when I realized that it doesn't work as is, and then got a new
test phase starting back in September. Except for minor bugs it seemed
to work rather well. Nobody reported this effect in all the 4 months
of
test period. You don't actually think I wouldn't have fixed it prior
to the release if I had known about it, do you?
2.4.0-1 was released ~3 weeks ago. I had actually upgraded a few days
earlier to a TEST version and noticed that a cygwin downloaded exe
couldn't be executed but assumed the exe was corrupt and didn't
investigate...
Then a few days ago the same thing happened again. Now I'm here.
Anyway, clearly most users are just that: users, and not testers that
will install and test TEST versions.
They are not supposed to be modifiable in Explorer. If you want to
change permissions on a Cygwin ACL, use chmod or setfacl.
Is this a joke?
Here is the output from icacls /saveacl for some file:
D:P(D;;RPWPDTRC;;;S-1-0-0)(A;;0x1f019f;;;S-1-5-21-559282050-488988736-2019639472-1001)(D;;WP;;;AU)(D;;WP;;;SY)(D;;WP;;;BA)(D;;WP;;;BU)(A;;FR;;;S-1-5-21-559282050-488988736-2019639472-513)(A;;0x1201bf;;;AU)(A;;0x1201bf;;;SY)(A;;0x1201bf;;;BA)(A;;0x1200a9;;;BU)(A;;FR;;;WD)
Doh, I'm sorry, but I can't read this format very well. Can you please
again send the standard icacls output as well as the output from
getfacl
of the parent dir and the created file? I'd like to have this problem
fixed, but I need your help. As I said, it works fine for me and
without
being able to reproduce I'm somewhat at a loss.
You can import this by putting it in a textfile and using icacls
testfile /restore acl.txt.
As I've said before, my Windows is German. icacls output will be
localized. Do you really want that?
What I posted is the only portable way to share ACLs.
Here is what's "normal" for Windows if I create a file under a new
folder on
C: in Explorer:
If you don't want POSIX perms, but standard Windows perms, use the
"noacl"
mount option. See
https://cygwin.com/cygwin-ug-net/using.html#mount-table
I guess that is my only option right now.
Here is what I would expect:
MyUser is in the group Administrators. Given the inherited
permissions above
a Windows-created file should be shown as "-rwxrwxr--+ MyUser
Administrators"?
Sorry, can't do that, *unless* you make "Administrators" the primary
group in your user token(*).
Ok, so the group is "None". No big deal.
So what about fixing the permissions like I described?
So the permissions would be "-rwx--+ MyUser None" in Cygwin for a
Windows-created file with default ACL.
By using the inherited default ACLs there should be at most 3 additional
ACLs (+1 for NULL SID whatever that is doing):
- deny r/w/x for user ("MyUser")
- allow r/w/x for group ("None")
- allow r/w/x for other ("Everyone")
And leaving the inherited ones untouched, right?
But if you scroll up you will see that in my system Cygwin kills the
inheritance and I end up with 12 new ACL entries for each file.
--
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
Re[2]: Issues with ACL settings after updating to the latest cygwin.dll
It is normal and was normal for at least seventeen years. That's a blatant lie. It never happened to me before, and I doubled checked this by installing the older 2.3. It didn't happen before 2.4. You'd be surprized… But the actual answer is "yes". I actually am surprised since you seem to have undergone a sex change and are now Corinna. You weren't asked for "portable". I didn't talk to you. You weren't asked anything. I find it quite rude that you feel the need to intrude into a discussion giving nonsensical know-it-all responses .. even on behalf of other people. I'll ignore further emails from you, thanks for wasting my time. -- 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
Re[2]: Issues with ACL settings after updating to the latest cygwin.dll
Not sure what Transmission is, but files downloaded with POSIX tools are usually not executable. For instance, download Cygwin's setup-x86.exe with wget. Then try to execute it. It won't since the permissions are set according to your umask and without execute permissions, e.g., 0644. This is normal. The behavior has changed with the ACL change in Cygwin and I would not consider that "normal". The warning from Windows is not normal. I realize that the previous implementation was already problematic and messed with permissions but I did not notice it since it never denied executing executables. The permissions must *not* be reordered. If Cygwin creates permissions incorrectly it's one thing, but the order to emulate POSIX permissions is non-canonical. Reordering them will break them. Please provide the exact output from icacls. They *have* to be reordered to be modifiable in Windows/Explorer. In other words, if I want to change permission the new ACL behavior ensures that it breaks the Cygwin permissions? Here is the output from icacls /saveacl for some file: D:P(D;;RPWPDTRC;;;S-1-0-0)(A;;0x1f019f;;;S-1-5-21-559282050-488988736-2019639472-1001)(D;;WP;;;AU)(D;;WP;;;SY)(D;;WP;;;BA)(D;;WP;;;BU)(A;;FR;;;S-1-5-21-559282050-488988736-2019639472-513)(A;;0x1201bf;;;AU)(A;;0x1201bf;;;SY)(A;;0x1201bf;;;BA)(A;;0x1200a9;;;BU)(A;;FR;;;WD) After letting Windows fix the order: D:PAI(D;;RPWPDTRC;;;S-1-0-0)(D;;WP;;;AU)(D;;WP;;;SY)(D;;WP;;;BA)(D;;WP;;;BU)(A;;0x1f019f;;;S-1-5-21-559282050-488988736-2019639472-1001)(A;;FR;;;S-1-5-21-559282050-488988736-2019639472-513)(A;;0x1201bf;;;AU)(A;;0x1201bf;;;SY)(A;;0x1201bf;;;BA)(A;;0x1200a9;;;BU)(A;;FR;;;WD) Here is what's "normal" for Windows if I create a file under a new folder on C: in Explorer: D:AI(A;ID;FA;;;BA)(A;ID;FA;;;SY)(A;ID;0x1200a9;;;BU)(A;ID;0x1301bf;;;AU) Strangely enough this is displayed as "-rwxrwx---+ MyUser None" with `ls -l` even though my user is in the group Administrators. Here is what I would expect: MyUser is in the group Administrators. Given the inherited permissions above a Windows-created file should be shown as "-rwxrwxr--+ MyUser Administrators"? After chmod 664 I would expect this: - still inherit all the permissions - add permission MyUser DENY execute - add permission Administrators DENY execute - add permission Everyone ALLOW read Instead Cygwin copies all permissions, drops the inheritance, copies them again, adds None, adds NULL SID ... After a consecutive chmod 770 I would expect the above non-inherited permissions to be removed again. -- 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
Re[2]: Issues with ACL settings after updating to the latest cygwin.dll
I'm not quite sure what you observe there. The NULL SID ACE only contains extra information about some POSIX bits and the MASK value. It's existence and setting should not influence what you can do with the file. The permission bits are explicitely set elsewhere in the ACL. Can you reproduce the issue so that I can see what's going on? I need the icacls output for the file and its parent directory, as well as the output from getfacl for both. I have the same problem with Transmission. I noticed this first when I tried to execute an exe that was downloaded with Transmission compiled in cygwin. When trying to start the exe from Explorer an error dialog will appear: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item." When going to file properties - security I get an information dialog window: "The permissions on are incorrectly ordered, which may cause some entries to be ineffective." Proper permissions (of parent folder) look like this: Authenticated Users: modify SYSTEM: Full control Administrators: Full control Users: Read & execute The permissions of the cygwin/transmission created files are (manually translated from German): NULL SID: special : special Authenticated Users: Browse folder / Execute file SYSTEM: Browse folder / Execute file Administrators: Browse folder / Execute file Users: Browse folder / Execute file Nobody: Read Authenticated Users: Read, write, execute SYSTEM: Read, write, execute Administrators: Read, write, execute Users: Read, Execute Everyone: Read Also when going to advanced permissions it shows the same incorrectly ordered warning and asks me to re-order permissions. -- 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
Re[3]: Issues with ACL settings after updating to the latest cygwin.dll
Nobody: Read Small correction, this entry is actually S-1-5-21-559282050-488988736-2019639472-513 which actually stalls the file properties window when switching to the security tab for a while. I guess Windows is trying to resolve this SID but gives up (there is no such SID on my system) and eventually replaces the display name with Nobody. Something is seriously broken here. -- 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
Re[3]: Issues with ACL settings after updating to the latest cygwin.dll
I have the same problem with Transmission. Sorry for another mail, but I need to make another last correction: It's not Transmission specific. A simple $ cd /cygdrive/path/to/download/dir $ touch test will result in the same broken permissions for test. Doing this in $HOME will result in these Windows permissions: NULL SID Everyone Nobody (actually non existent S-1-5-21-...) There are also no warnings and no prompt to re-order permissions. File permission for an older file (created before cygwin ACL changes): Everyone Nobody (actually non existent S-1-5-21-...) So the new ACL implementation simply messes up in directories with non-cygwin permissions. -- 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
Re: Compilation continuously increases (non) paged pool memory usage
What is leaking here? Here are some hard numbers: After the system booted up, nonpaged 70 MB, paged WS 208 MB. One compilation later: nonpaged 157MB, paged WS 289 MB. Another one later: 249 MB, 342 MB. At the moment I'm at 550 MB nonpaged, 650 MB paged WS. The number of system threads and handles remains about the same. poolmon shows the main growth of nonpaged memory with tag "Proc" (process objects) and paged with tag "Toke" (token objects). xperf shows cygwin1.dll under Proc. How could I debug better what is leaking here? -- 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
Re[2]: Compilation continuously increases (non) paged pool memory usage
Greetings, xnor! Hey. Usual suspects are BLODA. Most often, antiviruses of questionable origin and mental sanity. Try same tests on a separate system, or in a VM. That's the first thing I've checked. I don't have any anti virus/malware or firewall or similar software installed and I've even disabled Windows Defender. Will do some more checks... -- 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
Compilation continuously increases (non) paged pool memory usage
Hello, I've noticed on my system (Windows 10, Cygwin64) that a simple ./configure && make of a typical project increases the memory usage, both paged and non-paged pool. After the configure/make is done this memory continues to be used. In task manager memory usage will therefore slowly grow, depending on the projects by up to several GB. What is leaking here? Is it Windows' fault or Cygwin's? -- 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
