On May 30 16:50, Erik Soderquist wrote:
> On Mon, May 30, 2016 at 6:35 AM, Corinna Vinschen wrote:
> >
> > Can you, by any chance, also send the output of `cd /tmp; icacls .'?
> >
>
> Unfortunately no, corporate machine, and was replaced less than a week
> ago. The new machine does not have the s
On Mon, May 30, 2016 at 6:35 AM, Corinna Vinschen wrote:
>
> Can you, by any chance, also send the output of `cd /tmp; icacls .'?
>
Unfortunately no, corporate machine, and was replaced less than a week
ago. The new machine does not have the same issue, though I have not
tested (and probably won'
On Apr 29 12:03, Erik Soderquist wrote:
> I'm having a similar issue with strange acl results... I wish I knew
> which update triggered this, but I'd ignored and/or worked around
> it...
>
> I can reproduce it with the following:
>
> user@localhost ~
> $ touch /tmp/foo
>
> user@localhost ~
> $ c
I'm having a similar issue with strange acl results... I wish I knew
which update triggered this, but I'd ignored and/or worked around
it...
I can reproduce it with the following:
user@localhost ~
$ touch /tmp/foo
user@localhost ~
$ chmod 700 /tmp/foo
user@localhost ~
$ echo foo>/tmp/foo
-bash:
On Mar 7 20:12, aki...@free.fr wrote:
> Hi, Corinna
>
> Here an example of one problematic ACL
> Here on /etc directory (here on remote system)
> [...]
> # file: .
> # owner: Unknown+User
> # group: Unknown+Group
> user::rwx
> group::r-x
> other:r-x
> default:user::rwx
> default:group::r-x
> defa
Hi, Corinna
Here an example of one problematic ACL
Here on /etc directory (here on remote system)
$ cacls .
...\ws\njcyg\etc NULL SID:(DENY)(accès spécial :)
READ_CONTROL
F
R
Tout le monde:R
On Mar 5 18:49, aki...@free.fr wrote:
> Hi, Corinna
>
> To be clear about my problems about ACL.
> A very simple example to observe.
>
> I go to the root disk (C:\ or /cygdrive/c upon the system)
> I can't create a file here (normally protected).
> So I use administrator rights to do that with c
Hi, Corinna
To be clear about my problems about ACL.
A very simple example to observe.
I go to the root disk (C:\ or /cygdrive/c upon the system)
I can't create a file here (normally protected).
So I use administrator rights to do that with cmd and bash.
In cmd :
C:\>echo > xx
C:\>cacls xx
C:\xx
Hi Akiki(?),
On Mar 4 16:43, aki...@free.fr wrote:
> Hi,
> I have the different problems you have about this new security right NULL SID
> DENY added to some files.
I still doubt the NULL ACE is the actual culprit of whatever you
observe. A NULL ACE doesn't affect your permissions, unless you
Hi,
I have the different problems you have about this new security right NULL SID
DENY added to some files.
Sometimes also Windows can't access files concerned.
He considered security rigths unordered and I have to class them before
continue.
It's too difficult for me to help you to correct the p
On Feb 10 18:17, xnor wrote:
>
> >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.
It was already the case before. It depends on the POSIX permissions
which have to
Greetings, xnor!
>>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.
"Never happened to you" does not equal "wasn't the case".
Your presumptuou
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
Greetings, xnor!
>>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.
It is normal and was normal for at least seventeen years.
>>Come on, be fair. The new ACL h
Greetings, xnor!
>>It was always the case.
>>Permissions are NOT REQUIRED to be ordered in a specific way, but
>>Explorer is
>>only capable of editing them in the only one way.
>>Means, Explorer is deficient. Explorer. Not Windows. Windows is
>>perfectly
>>capable of handling the Cygwin ACL in
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
It was always the case.
Permissions are NOT REQUIRED to be ordered in a specific way, but
Explorer is
only capable of editing them in the only one way.
Means, Explorer is deficient. Explorer. Not Windows. Windows is
perfectly
capable of handling the Cygwin ACL in the intended way.
No, it re
On Feb 10 12:55, Corinna Vinschen wrote:
> On Feb 9 20:53, xnor wrote:
> > 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,
On Feb 9 10:01, K Stahl wrote:
> On Feb 8, 2016 1:33 PM, "xnor" wrote:
> >
> >
> >> 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
> > $ tou
On Feb 9 20:53, xnor wrote:
>
> >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
Greetings, xnor!
>>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
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 i
On Feb 8, 2016 1:33 PM, "xnor" wrote:
>
>
>> 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 permissio
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
On Feb 8 18:12, xnor wrote:
>
> >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
On Feb 8 17:48, xnor wrote:
>
> >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
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) an
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 reproduc
On Jan 29 17:52, K Stahl wrote:
> I've discovered that when I use cvs to pull a module, the security
> settings on the created files and directories are incorrect. When I
> view the security settings of the files, I noticed an invalid "NULL
> SID" group permission was added. If I delete this valu
I've discovered that when I use cvs to pull a module, the security
settings on the created files and directories are incorrect. When I
view the security settings of the files, I noticed an invalid "NULL
SID" group permission was added. If I delete this value, I can
properly execute the file, but
30 matches
Mail list logo
