X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26223586.post@talk.nabble.com> Date: Thu, 5 Nov 2009 14:43:14 -0800 (PST) From: aputerguy To: cygwin AT cygwin DOT com Subject: [1.7] Do the new security enhancements allow ssh under your own $USERNAME MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 I read the materials in "What's New" and the section "Windows Security in Cygwin" with interest since it describes new authentication potentials. However, I did not understand the material well enough to know whether 1.7 will allow users to ssh under their own $USERNAME or whether you will always get USERNAME=SYSTEM (assuming that you started sshd normally with cygrunsrv). I use 'ssh' to log on to remote computers to initialize backups by setting up shadow mounts. However, since vshadow won't run as user SYSTEM, I have to go through crazy hoops using 'at' to launch the process at the next minute in the future so that I can get vshadow to run. This ssh/security limitation is odd coming from a *nix environment where ssh gives you all the power you want or need... -- View this message in context: http://old.nabble.com/-1.7--Do-the-new-security-enhancements-allow-ssh-under-your-own-%24USERNAME-tp26223586p26223586.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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