Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <42FA807F.3B0A4F78@dessent.net> Date: Wed, 10 Aug 2005 15:32:31 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: difference in permissions, using two SSH authentication methods: public key/password References: <20050810113433 DOT GA20506 AT mail DOT zend DOT com> <42F9ED84 DOT A0B53889 AT dessent DOT net> <20050810143156 DOT GA18482 AT mail DOT zend DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Michael Spector wrote: > May be this question is not for this maillist, so please excuse me: > > Is there a way of disabling this NTSEC security mechanism? > I mean: is there a way of accessing shared disks without logging in with password? > > I tried setting CYGWIN=nontsec, but the situation is the same. As Corinna already said, you will need to provide the password one way or another for network share authentication. You can do this by giving it directly to 'net use', or you can run the sshd service as the desired user. In this case you will give the password for the user when installing the service, and there will be no user context switching necessary. The token for the service will already contain the password, so it should be possible to access network shares using passwordless ssh auth. The downside is that you will only ever be able to log in as that user. (Both because regular user accounts lack the privileges to switch user contexts and because doing so would just result in the same problem of a token lacking a password.) Brian -- 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/