X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <005c01c87584$518c6f30$2e08a8c0@CAM.ARTIMI.COM> <012c01c876f1$94f095d0$2e08a8c0@CAM.ARTIMI.COM> Subject: RE: chmod o-r woes... Date: Mon, 25 Feb 2008 10:43:44 -0000 Message-ID: <003601c8779b$4af55f10$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 25 February 2008 10:36, Marc Girod wrote: >> So, try your original test again, but with >> >> ~> export CYGWIN=ntsec smbntsec >> >> at the start. > > Thanks. This helpped. > I didn't even have to give the chmod again. > With the environment variable, the rights showed up correctly. > [I now set this to my .bash_profile] I always set my basic CYGWIN settings in the windows system properties global environment. > Which is of course worrisome: in order to read my password, > on just needs to unset the CYGWIN environment variable... If the remote drive supports proper NTFS ACLs, any file cygwin creates on it /while/ CYGWIN=smbntsec is in effect will have proper NTFS access permissions, so, e.g. if it has rwx------, it will only have access permissions for your windows user account. You might want to chmod -R 700 (or whatever group/world perms you'd prefer) your home drive to make sure nobody can go snooping. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/