X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <46E7FB17 DOT 3030904 AT scranton DOT edu> Subject: RE: sftp removing writable bit Date: Thu, 13 Sep 2007 17:04:29 +0100 Message-ID: <016601c7f61f$c3d6ecd0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <46E7FB17.3030904@scranton.edu> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 12 September 2007 15:44, John J. Culkin wrote: > Hello > > I am seeing an issue with Cygwin's sftp. It seems that after I upload a > file that overwrites an existing file, the writable bit is removed. This > prevents me from uploading a new version of the file. > > The files are owned by the SFTP user. > > Any Ideas? Is it because you made a wrapper script on the server that sets the umask to 002 before starting the sftp server, by any chance? 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/