X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <480ECBF1.1030000@cwilson.fastmail.fm> Date: Wed, 23 Apr 2008 01:41:05 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: ssh-agent, keychain, and Vista [Was: Re: Vista + cygwin basics] References: <480EC85C.1020901@cwilson.fastmail.fm> In-Reply-To: <480EC85C.1020901@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Charles Wilson wrote: > It seems to do what I want, but as you say, keychain does slow down the > login process quite a bit. Other drawbacks to my approach: > (1) the console user's ssh-agent does not survive logoff (but remote > logons' ssh-agents do, since they all live in session 0). > (2) non-standard, win32-specific patch to /usr/bin/keychain And, of course, the advantage over Karl's approach is: (1) you don't need to grant "Log on as a service" privilege to regular users (2) you don't need administrator privileges to set it up (e.g. to grant the privilege above to untrusted users, and to install ssh-agent as a service). -- Chuck -- 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/