Group execute permission regression (??): causing problem in fossil.

Group execute permission regression (??): causing problem in fossil.

[Jan Nijtmans]

Hi All,

Starting with the upgrade to Cygwin (latest: 1.7.34), fossil started to
behave strangely: Every file committed to a fossil repository suddenly
had the execute permission bit set! With 1.7.33 this didn't happen.
The cause of this problem was that apparently starting with Cygwin
1.7.34, the group permission bit in some directories is always set, and
cannot be unset. For example from my checked-out fossil repository:

    nijtmaj <path>/workspace/fossil
    $ ls -la .fossil-settings
    total 20
    drwxrwxr-x+ 1 nijtmaj None   0 Feb  6 16:48 .
    drwxrwxr-x+ 1 nijtmaj None   0 Feb  6 16:48 ..
    -rw-rwxr--+ 1 nijtmaj None 140 Feb  6 16:48 clean-glob
    -rw-rwxr--+ 1 nijtmaj None  55 Feb  6 16:48 encoding-glob
    -rw-rwxr--+ 1 nijtmaj None  61 Feb  6 16:48 ignore-glob
    -rw-rwxr--+ 1 nijtmaj None  61 Feb  6 16:48 keep-glob

    nijtmaj <path>/workspace/fossil
    $ chmod a-x .fossil-settings/*

    nijtmaj <path>/workspace/fossil
    $ ls -la .fossil-settings
    total 20
    drwxrwxr-x+ 1 nijtmaj None   0 Feb  6 16:48 .
    drwxrwxr-x+ 1 nijtmaj None   0 Feb  6 16:48 ..
    -rw-rwxr--+ 1 nijtmaj None 140 Feb  6 16:48 clean-glob
    -rw-rwxr--+ 1 nijtmaj None  55 Feb  6 16:48 encoding-glob
    -rw-rwxr--+ 1 nijtmaj None  61 Feb  6 16:48 ignore-glob
    -rw-rwxr--+ 1 nijtmaj None  61 Feb  6 16:48 keep-glob


For some reason, the group execute permission bit of those
files is always set, and cannot be unset.

When fossil commits a file, it looks at the current file
permissions (either user, group or other) here:
      <http://www.fossil-scm.org/index.html/artifact/6c218bb03870305f?ln=253>
that's where the sudden change comes from.

A workaround for this problem is committed in fossil now, but it's puzzling
to me why this happens. Not all directories behave like this, so it
probably has a relation with permissions .......

Hoping someone can shine a light on that!

Regards,
      Jan Nijtmans

--
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: Group execute permission regression (??): causing problem in fossil.

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On Feb  6 17:22, Jan Nijtmans wrote:
> Hi All,
> 
> Starting with the upgrade to Cygwin (latest: 1.7.34), fossil started to
> behave strangely: Every file committed to a fossil repository suddenly
> had the execute permission bit set! With 1.7.33 this didn't happen.
> The cause of this problem was that apparently starting with Cygwin
> 1.7.34, the group permission bit in some directories is always set, and
> cannot be unset.

https://cygwin.com/ml/cygwin-announce/2015-02/msg00009.html
https://cygwin.com/faq/faq.html#faq.using.ssh-pubkey-stops-working

Does that help?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Group execute permission regression (??): causing problem in fossil.

[Achim Gratz]

Jan Nijtmans writes:
> Starting with the upgrade to Cygwin (latest: 1.7.34), fossil started to
> behave strangely: Every file committed to a fossil repository suddenly
> had the execute permission bit set! With 1.7.33 this didn't happen.
> The cause of this problem was that apparently starting with Cygwin
> 1.7.34, the group permission bit in some directories is always set, and
> cannot be unset. For example from my checked-out fossil repository:

Most likely default permissions foisted by Windows via ACL (note that +
character after the permission string from ls?).  Try 'setfacl -b'

> A workaround for this problem is committed in fossil now, but it's puzzling
> to me why this happens. Not all directories behave like this, so it
> probably has a relation with permissions .......

Instead of workarounds, teach fossil to understand ACL.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
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: Group execute permission regression (??): causing problem in fossil.

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

On Feb  6 17:54, Achim Gratz wrote:
> Jan Nijtmans writes:
> > Starting with the upgrade to Cygwin (latest: 1.7.34), fossil started to
> > behave strangely: Every file committed to a fossil repository suddenly
> > had the execute permission bit set! With 1.7.33 this didn't happen.
> > The cause of this problem was that apparently starting with Cygwin
> > 1.7.34, the group permission bit in some directories is always set, and
> > cannot be unset. For example from my checked-out fossil repository:
> 
> Most likely default permissions foisted by Windows via ACL (note that +
> character after the permission string from ls?).  Try 'setfacl -b'

...or setfacl -k for the directories only.  Don't forget the option
I implemented just because you asked for it :)


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Group execute permission regression (??): causing problem in fossil.

[Achim Gratz]

Corinna Vinschen writes:
> ...or setfacl -k for the directories only.  Don't forget the option
> I implemented just because you asked for it :)

Sure. ;-) But without the ACl we don't know and 'setfacl -b' is a bit
safer.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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: Group execute permission regression (??): causing problem in fossil.

[Jan Nijtmans]

2015-02-06 17:35 GMT+01:00 Corinna Vinschen:
> https://cygwin.com/ml/cygwin-announce/2015-02/msg00009.html
> https://cygwin.com/faq/faq.html#faq.using.ssh-pubkey-stops-working
>
> Does that help?
>
>
> Corinna

Yes, that makes perfect sense. Thank You!

Regards,
        Jan Nijtmans

--
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: Group execute permission regression (??): causing problem in fossil.

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

On Feb  6 20:59, Jan Nijtmans wrote:
> 2015-02-06 17:35 GMT+01:00 Corinna Vinschen:
> > https://cygwin.com/ml/cygwin-announce/2015-02/msg00009.html
> > https://cygwin.com/faq/faq.html#faq.using.ssh-pubkey-stops-working
> >
> > Does that help?
> >
> >
> > Corinna
> 
> Yes, that makes perfect sense. Thank You!

No worries.  I guess I should revamp the FAQ to add a more generic

  Why do my files have certain group permissions and chmod doesn't help?

entry.  I just didn't expect that this change would create problems with
other tools than ssh or rlogin :|


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]