Cygwin file permission issues
I've run into a Cygwin permissions issue that I haven't been able to resolve by looking through past discussions. When a file file or folder is created by a user under cygwin, it isn't adhering to the permissions inherited by parent folders. Based on the parent folder, any folders and files created should have full access by all users, but they aren't writable. When I go to the Security tab under Windows I get: The permissions on [file/folder name] are incorrectly ordered, which may cause some entries to be ineffective. Press OK to continue and sort the permissions correctly, or Cancel to reset the permissions. Based on the description of this error message, the result of selecting OK or Cancel seem to indicate something is going to change (sorting, or reseting), so I'm not sure what the actual permissions are from the Windows point of view. When I select OK, I see a bunch of entries that shouldn't be there based on the permissions of the parent folder. When I select Cancel, it shows that 'Everyone' has full control. I've messed around with setting CYGWIN to ntsec an nontsec to see if that affects anything, but neither of these settings seem to affect the way the permissions are assigned for new files. How do I fix this? -- 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: Cygwin file permission issues
Are you setting permissions in cygwin with a 2775 on directories? Its my understanding the cygwin dll overwrites the windows permissions mode in favor of its own. So then you have to use set gid or set uid on the directory Hope this helps -R I haven't tried this, but wouldn't this just affect the owner of the file? If so, this isn't really what I'm after. What I'm looking for is a way to ensure that all files and folders created have full access for 'Domain Users'. -- 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: Cygwin file permission issues
Thanks Jeremy, this seems to have resolved the issue. For those who might stumble upon this in the future, here's exactly what I ended up doing: 1. Edit the /etc/fstab file 2. Added the following line (note: our install of Cygwin is on the X drive): X:/cygwin / ntfs override,binary,noacl 0 0 3. Closed and reopened the bash shell. 4. Changed to the folder in question and issued a 'touch' command to create a test file. 5. Opened the properties on the newly created file through Windows Explorer and verified that the permissions were correctly being inherited from the parent folder. Derek On Wed, Jun 30, 2010 at 12:24 PM, Jeremy Bopp jer...@bopp.net wrote: On 6/30/2010 11:27 AM, Derek Greer wrote: I've run into a Cygwin permissions issue that I haven't been able to resolve by looking through past discussions. When a file file or folder is created by a user under cygwin, it isn't adhering to the permissions inherited by parent folders. Based on the parent folder, any folders and files created should have full access by all users, but they aren't writable. When I go to the Security tab under Windows I get: The permissions on [file/folder name] are incorrectly ordered, which may cause some entries to be ineffective. Press OK to continue and sort the permissions correctly, or Cancel to reset the permissions. Read the following sections of the User's guide: http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files http://cygwin.com/cygwin-ug-net/using.html#using-pathnames The short and sweet is that this is the intended behavior of Cygwin, but you can work around it by ensuring that the noacl option is set on the mountpoint under which the target file resides. You may need/want to create a new mountpoint just for the files of interest. -Jeremy -- 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 -- 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: Cygwin 1.7.x upgrade: Xterm history messes up prompt
I discovered that the problem is specific to my PS1 settings, but a bug
nevertheless. The prompt I've used for years is:
PS1='\[\033]0;\w\007\033[32m\][\h]: \[\033[33m ${PWD##*/}\033[0m\] '
This shows [current machine] : current folder where the current machine
is greenish and the current folder is yellowish. Something about the latest
version doesn't like the special characters that produce the colors anymore
... at least how I have them specified.
--
View this message in context:
http://old.nabble.com/Cygwin-1.7.x-upgrade%3A-Xterm-history-messes-up-prompt-tp27163806p27180596.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: startxwin.exe without lingering DOS window
How do you run startxwin.exe so that it doesn't leave a lingering MS-DOS window after it starts the programs in ~/.startwinrc? C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe This can't be correct, as this is what exactly what the X Server start menu link executes and it spawns the the vanilla XTerm window. I always customized by startxwin.bat to not launch this window. How is this done with the new startxwin.exe? -- View this message in context: http://old.nabble.com/startxwin.exe-without-lingering-DOS-window-tp27052469p27163006.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: startxwin.exe without lingering DOS window
If you don't want the server to start an xterm by itself, create an empty ~/.startxwinrc file Ah, ok. For some reason I mistakenly read the original question as how do you get startxwin.exe to not show the default XTerm where the user was actually talking about a spawning DOS window. Thanks. -- View this message in context: http://old.nabble.com/startxwin.exe-without-lingering-DOS-window-tp27052469p27165520.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Subversion not caching password
Using the Cygwin version of subversion, I have been unable to
configure it to store my encrypted password in
~/.subversion/auth/svn.simple/.
Here are the steps I am taking (the first step to start with a clean config):
- rm -rf ~/.subversion; svn --version
- edit the ~/.subversion/servers file to include store-passwords =
yes and store-plaintext-passwords = no under the [global] section.\
After following these steps, running svn up from a subversion work
area, I am getting the first expected prompt to accept the certificate
and prompting me for my password. I select 'p' for permanently accept
certificate and enter my password which works as expected. Issuing
the command again prompts me for my password again.
Examining the ~/.subversion/auth/svn.simple/ folder, a file a
successfully been created with the information for the authentication
realm, but this file does not contain the encrypted password.
What am I missing?
EXTRA INFO
---
Another thing I've tried is editing the ~/.subversion/config file and
adding a password-stores = windows-cryptoapi under the [auth]
section. This seems to have no effect.
I would also note that I also have VisualSVN installed on my machine
and when using that version it does not prompt me for my password.
Looking at its config store, It has generated the exact same named
authentication realm file under ${HOMEPATH}/Application\
Data\Subversion\auth\svn.simple\, but contains the encrypted password
section. Copying the contexts of this file the corresponding file
within ~/.subversion/auth/svn.simple/ also has had no effect, as
issuing a svn up command prompts for my password which then
overwrites the ~/.subversion/auth/svn.simple file with the previous,
non-password containing contexts again.
For those tempted to answer with Just use the VisualSVN version (I'm
sure no one out there is thinking that), aside from this not being the
stated problem (not being able to get the Cygwin subversion to cache
passwords), there are also issues with using the VisualSVN version
from the bash shell (things like it not accepting commands after
prompting for merge operations).
Thanks for any help that can be provided. Hopefully there is some
simple you need to uncomment this other property and set it to X
answer to this.
--
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: Subversion not caching password
Very cool. Thanks much! Derek -Original Message- From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of David Rothenberger Sent: Tuesday, July 07, 2009 10:11 PM To: cygwin@cygwin.com Subject: Re: Subversion not caching password On 7/7/2009 4:39 PM, David Rothenberger wrote: On 7/7/2009 3:04 PM, Derek Greer wrote: Using the Cygwin version of subversion, I have been unable to configure it to store my encrypted password in ~/.subversion/auth/svn.simple/. I will look into supporting the wincrypt API in the Cygwin build, but I wouldn't hold your breath if I were you. Turns out this wasn't too hard. I'm working on packaging 1.6.3, so I'll include this fix in those packages. They should be available early next week if not before. -- David Rothenberger daver...@acm.org Volunteer Cygwin subversion maintainer. -- 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 -- 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
