Bash script permissions

Bash script permissions

[David Monk]

I am running the latest net realease on NT 4 and Win 2k. I am having a
problem limiting, from cygwin, the permissions on a bash script so that only
the owner can execute it.
I finally after much fiddling figured out that with the shebang line in the
script, cygwin immediately thinks it's executable by all. If I try any chmod
affecting it's executable status, it's ignored. How can I work around this?
Also, how can this be worked around on Win9x also, as it is planned to
eventually distribute this script set.

Thanks,
David Monk CCNA. MCSE
david@purplebear.net




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Larry Hall (RFK Partners, Inc)]

At 03:50 PM 9/12/2001, David Monk wrote:
>I am running the latest net realease on NT 4 and Win 2k. I am having a
>problem limiting, from cygwin, the permissions on a bash script so that only
>the owner can execute it.
>I finally after much fiddling figured out that with the shebang line in the
>script, cygwin immediately thinks it's executable by all. If I try any chmod
>affecting it's executable status, it's ignored. How can I work around this?


Set ntsec in your CYGWIN environment before starting any Cygwin app.


>Also, how can this be worked around on Win9x also, as it is planned to
>eventually distribute this script set.


You can't.  9x has no concept of security. 



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Corinna Vinschen]

On Wed, Sep 12, 2001 at 02:50:30PM -0500, David Monk wrote:
> I am running the latest net realease on NT 4 and Win 2k. I am having a
> problem limiting, from cygwin, the permissions on a bash script so that only
> the owner can execute it.
> I finally after much fiddling figured out that with the shebang line in the
> script, cygwin immediately thinks it's executable by all. If I try any chmod
> affecting it's executable status, it's ignored. How can I work around this?
> Also, how can this be worked around on Win9x also, as it is planned to
> eventually distribute this script set.

On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
Where there's no security at all...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[David Monk]

> On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
> Where there's no security at all...

There are problems with this approach. When I set ntsec in the CYGWIN
environment variable, everything is now marked as executable. And I DO mean
everything. It would be a nightmare to manually go through and change
permissions on everything.

Maybe Cygwin won't be able to be a supported platform after all.

Thanks anyway,
David Monk CCNA, MCSE
david@purplebear.net




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Larry Hall (RFK Partners, Inc)]

At 04:35 PM 9/12/2001, David Monk wrote:
> > On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
> > Where there's no security at all...
>
>There are problems with this approach. When I set ntsec in the CYGWIN
>environment variable, everything is now marked as executable. And I DO mean
>everything. It would be a nightmare to manually go through and change
>permissions on everything.


Did you have a snapshot DLL on your system at any time?  That might explain
what you see.  The behavior you describe is not typical.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[David Monk]

The only cygwin1.ddl this system has ever seen is the one I installed via
setup.exe from http://sources.redhat.com/cygwin/

David Monk


----- Original Message -----
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "David Monk" <david@purplebear.net>; <cygwin@cygwin.com>
Sent: Wednesday, September 12, 2001 3:47 PM
Subject: Re: Bash script permissions


> At 04:35 PM 9/12/2001, David Monk wrote:
> > > On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
> > > Where there's no security at all...
> >
> >There are problems with this approach. When I set ntsec in the CYGWIN
> >environment variable, everything is now marked as executable. And I DO
mean
> >everything. It would be a nightmare to manually go through and change
> >permissions on everything.
>
>
> Did you have a snapshot DLL on your system at any time?  That might
explain
> what you see.  The behavior you describe is not typical.
>
>
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 118 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
>
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Larry Hall (RFK Partners, Inc)]

OK, I can't explain the behavior you see with ntsec enabled then.

Sorry.

Larry


At 04:50 PM 9/12/2001, David Monk wrote:
>The only cygwin1.ddl this system has ever seen is the one I installed via
>setup.exe from http://sources.redhat.com/cygwin/
>
>David Monk
>
>
>----- Original Message -----
>From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
>To: "David Monk" <david@purplebear.net>; <cygwin@cygwin.com>
>Sent: Wednesday, September 12, 2001 3:47 PM
>Subject: Re: Bash script permissions
>
>
> > At 04:35 PM 9/12/2001, David Monk wrote:
> > > > On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
> > > > Where there's no security at all...
> > >
> > >There are problems with this approach. When I set ntsec in the CYGWIN
> > >environment variable, everything is now marked as executable. And I DO
>mean
> > >everything. It would be a nightmare to manually go through and change
> > >permissions on everything.
> >
> >
> > Did you have a snapshot DLL on your system at any time?  That might
>explain
> > what you see.  The behavior you describe is not typical.
> >
> >
> > Larry Hall                              lhall@rfk.com
> > RFK Partners, Inc.                      http://www.rfk.com
> > 118 Washington Street                   (508) 893-9779 - RFK Office
> > Holliston, MA 01746                     (508) 893-9889 - FAX
> >
> >


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Corinna Vinschen]

On Wed, Sep 12, 2001 at 03:35:33PM -0500, David Monk wrote:
> > On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it.
> > Where there's no security at all...
> 
> There are problems with this approach. When I set ntsec in the CYGWIN
> environment variable, everything is now marked as executable. And I DO mean
> everything. It would be a nightmare to manually go through and change
> permissions on everything.

Apparently you don't seem to understand the concept of NTFS security
and _why_ it's set that way after switching ntsec on. Besides the
Microsoft documentation read http://cygwin.com/cygwin-ug-net/ntsec.html .
Thinko:  When Cygwin has been installed using no security settings at
att, how are the default settings on the files...

> Maybe Cygwin won't be able to be a supported platform after all.

It could depend on the developer of the application, too, not only
on the developer of the underlying system...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[David Monk]

> Apparently you don't seem to understand the concept of NTFS security
> and _why_ it's set that way after switching ntsec on. Besides the
> Microsoft documentation read http://cygwin.com/cygwin-ug-net/ntsec.html .
> Thinko:  When Cygwin has been installed using no security settings at
> att, how are the default settings on the files...
>

I would actually, considering my environment, love to switch to using the
ntsec setting. But, how do I change over to the new setting without a whole
ton of work? I have made so many additions to cygwin since original
installation here.

David Monk



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Christopher Faylor]

On Wed, Sep 12, 2001 at 04:01:24PM -0500, David Monk wrote:
>> Apparently you don't seem to understand the concept of NTFS security
>> and _why_ it's set that way after switching ntsec on. Besides the
>> Microsoft documentation read http://cygwin.com/cygwin-ug-net/ntsec.html .
>> Thinko:  When Cygwin has been installed using no security settings at
>> att, how are the default settings on the files...
>>
>
>I would actually, considering my environment, love to switch to using the
>ntsec setting. But, how do I change over to the new setting without a whole
>ton of work? I have made so many additions to cygwin since original
>installation here.

chmod -R a-x /lib /etc
etc.
Leave the directories containing binary files alone.

You don't have to laboriously do a chmod for every file.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[David Monk]

> chmod -R a-x /lib /etc
> etc.
> Leave the directories containing binary files alone.
>
> You don't have to laboriously do a chmod for every file.
>
> cgf

This is great and all, but it will leave any subdirectories thereunder
inaccessible until +x is set on them.

David Monk




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Rick Rankin]

How 'bout "find . -type d | xargs chmod a+x" to fix the directory settings.

--Rick
--- David Monk <david@purplebear.net> wrote:
> > chmod -R a-x /lib /etc
> > etc.
> > Leave the directories containing binary files alone.
> >
> > You don't have to laboriously do a chmod for every file.
> >
> > cgf
> 
> This is great and all, but it will leave any subdirectories thereunder
> inaccessible until +x is set on them.
> 
> David Monk
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Corinna Vinschen]

On Wed, Sep 12, 2001 at 02:45:30PM -0700, Rick Rankin wrote:
> How 'bout "find . -type d | xargs chmod a+x" to fix the directory settings.

And then setting the permissions on files will need another
similar command.  Shouldn't be too hard to figure that out
by yourself using manpages and all...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Properly using ntsec, from the beginning

[David Monk]

How would one go about doing a fresh install on NTFS, whether it be NT or
2000, and use the ntsec option of CYGWIN properly, without having to
immediately change file and directory permissions throughout?
IOW, is there a proven method to install Cygwin and get a proper filesystem
tree with permissions on text files, configuration files, and executable
scripts set similar to a typical UNIX filesystem? And also have proper
permission manipulation within cygwin.

David Monk



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Properly using ntsec, from the beginning

[Corinna Vinschen]

On Thu, Sep 13, 2001 at 08:30:41AM -0500, David Monk wrote:
> How would one go about doing a fresh install on NTFS, whether it be NT or
> 2000, and use the ntsec option of CYGWIN properly, without having to
> immediately change file and directory permissions throughout?
> IOW, is there a proven method to install Cygwin and get a proper filesystem
> tree with permissions on text files, configuration files, and executable
> scripts set similar to a typical UNIX filesystem? And also have proper
> permission manipulation within cygwin.

Setup.exe is not ntsec aware currently and since NT doesn't support
setting POSIX permissions by default, the answer is no.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Properly using ntsec, from the beginning

[Gerrit P. Haase]

David Monk schrieb am 2001-09-13, 8:30:

>How would one go about doing a fresh install on NTFS, whether it be NT or
>2000, and use the ntsec option of CYGWIN properly, without having to
>immediately change file and directory permissions throughout?
>IOW, is there a proven method to install Cygwin and get a proper filesystem
>tree with permissions on text files, configuration files, and executable
>scripts set similar to a typical UNIX filesystem? And also have proper
>permission manipulation within cygwin.

Mike Erdely has written a script to fix the permissions 
after a fresh install.

Gerrit

-- 
Here is the script:
http://www.cygwin.com/ml/cygwin/2001-04/msg01668.html


-- 
=^..^=

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash script permissions

[Gerrit P. Haase]

David Monk schrieb am 2001-09-12, 14:50:

>I am running the latest net realease on NT 4 and Win 2k. I am having a
>problem limiting, from cygwin, the permissions on a bash script so that only
>the owner can execute it.
>I finally after much fiddling figured out that with the shebang line in the
>script, cygwin immediately thinks it's executable by all. If I try any chmod
>affecting it's executable status, it's ignored. How can I work around this?

set CYGWIN=ntsec

>Also, how can this be worked around on Win9x also, as it is planned to
>eventually distribute this script set.

There are no permissions on win98. Everyone is allowed to do everything.

Gerrit


-- 
=^..^=

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/