There we go, a proper patch. It adds two command line parameters:
-f --no-acl-files
-F --no-acl-dirs
I could not figure if that's possible to share single variable between
two source files, so I just used two variables. At least it works as
intended and covers every situation.
On Thu, Sep 2, 201
On Fri, Sep 3, 2010 at 12:49 AM, Andy Koppe wrote:
> How did you find the problematic permissions? By looking at the
> security tab of the file properties? Did you confirm that users really
> were able to modify files they weren't supposed to? Could the
> offending privileges have been inherited f
On 9/2/2010 4:49 PM, Andy Koppe wrote:
> How did you find the problematic permissions? By looking at the
> security tab of the file properties?
Remember that the security tab has the very bad habit of re-ordering the
ACLs -- but the effect of ACLs is order dependent. Hence, just looking
at the per
On 2 September 2010 16:05, Vasya Pupkin wrote:
> In my case, these additional permissions were allowing everyone to
> modify files. Not harmful at all, indeed. I do not remember all the
> details, I remember these permissions were everywhere. So I just
> replaced everything with proper permissions
On Thu, Sep 2, 2010 at 8:25 PM, Jeremy Bopp wrote:
> Your answer was simply an assertion that there possibly was and may
> still be something wrong with the permissions handling under Cygwin, but
> that you also haven't confirmed that recently. The details really would
> be helpful and likely nec
On 9/2/2010 10:05 AM, Vasya Pupkin wrote:
> If you read again very carefully, you will see that I modified
> permissions AFTER I noticed they were messed up. Ok?
I tried to point out that your definition of "messed up" is the opposite
of Andy's. To you, the default permissions provided by setup.e
If you read again very carefully, you will see that I modified
permissions AFTER I noticed they were messed up. Ok?
In my case, these additional permissions were allowing everyone to
modify files. Not harmful at all, indeed. I do not remember all the
details, I remember these permissions were ever
On 9/2/2010 12:49 AM, Vasya Pupkin wrote:
> No, it wasn't a mess of my own making. I did not ever touch
> permissions, and it was a clean install. I don't know where these
> permissions came from, but ls -l displayed something like that for
> most files:
I read Andy's comment to mean that the mess
No, it wasn't a mess of my own making. I did not ever touch
permissions, and it was a clean install. I don't know where these
permissions came from, but ls -l displayed something like that for
most files:
drwxr-xr-x+ 1 user group 0 2010-09-02 09:32 tests
This "+" sign after permissions strin
Will do as soon as I get this thing to at least compile. Actually,
since there is no abstract layer for nt_wfopen(), all calls to this
function have to be modified. Alternatively, the function can be
modified to ignore perms parameter and alternative version of
setup.exe can be compiled then. That
On Thu, Sep 02, 2010 at 06:08:37AM +0400, Vasya Pupkin wrote:
>Because I prefer to keep things under control. And I don't think it
>will require a huge amount of work to disable working with permissions
>in setup.exe with command line switch.
Well, go ahead then. What are you waiting for? Send u
On 2 September 2010 03:08, Vasya Pupkin wrote:
> Because I prefer to keep things under control
Oh $DEITY.
> And I don't think it
> will require a huge amount of work to disable working with permissions
> in setup.exe with command line switch. I started to worry about it
> because cygwin failed so
Because I prefer to keep things under control. And I don't think it
will require a huge amount of work to disable working with permissions
in setup.exe with command line switch. I started to worry about it
because cygwin failed so much with permissions, having both
cygwin-specific and inherited one
On 1 September 2010 15:18, Vasya Pupkin wrote:
>> Do creating any entries in /etc/passwd or /etc/group or /etc/fstab
>> files can overcome this...
>
> Nothing can overcome thins until setup.exe is modified to support
> noacl option in /etc/fstab or get a similar comman line parameter or
> even a c
On 1 September 2010 09:00, Harie Ram wrote:
> I am currently packaging Cygwin 1.7 i.e. bundling all the files into
> an msi and installing it. The requirement is : install only the basic
> cygwin packages. Provide permissions to the Cygwin users so that they
> can install the packages that they req
Nothing can overcome thins until setup.exe is modified to support
noacl option in /etc/fstab or get a similar comman line parameter or
even a checkbox.
On Wed, Sep 1, 2010 at 6:00 PM, Harie Ram wrote:
> Do creating any entries in /etc/passwd or /etc/group or /etc/fstab
> files can overcome this.
Do creating any entries in /etc/passwd or /etc/group or /etc/fstab
files can overcome this...
Thanks
On Wed, Sep 1, 2010 at 7:21 PM, Vasya Pupkin wrote:
> Cygwin uses NTFS ACLs to imitate POSIX style permissions. It can also
> be configured to not touch ACL's at all, but setup program ignores
>
Cygwin uses NTFS ACLs to imitate POSIX style permissions. It can also
be configured to not touch ACL's at all, but setup program ignores
that and messes up permissions every time something is
installed/updated.
On Wed, Sep 1, 2010 at 4:49 PM, Rolf Campbell
wrote:
> On 2010-09-01 04:00, Harie Ram
On 2010-09-01 04:00, Harie Ram wrote:
The issue that I am currently facing is : the modify permissions given
to the INSTALLDIR "C:\Cygwin" using the msi lock permission table is
being inherited through all the subfolders and files. Any new manually
created folders and files anywhere within C:\Cyg
Date: Tue, Aug 31, 2010 at 8:11 PM
> Subject: Windows File permissions are not being inherited - Cygwin 1.7
> - Windows 7
> To: cygwin-i...@cygwin.com
>
>
> Hi ,
>
> I am currently packaging Cygwin 1.7 i.e. bundling all the files into
> an msi and installing it. The req
-- Forwarded message --
From: Harie Ram
Date: Tue, Aug 31, 2010 at 8:11 PM
Subject: Windows File permissions are not being inherited - Cygwin 1.7
- Windows 7
To: cygwin-i...@cygwin.com
Hi ,
I am currently packaging Cygwin 1.7 i.e. bundling all the files into
an msi and
21 matches
Mail list logo
