X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A512D14.9080406@gmail.com> Date: Sun, 05 Jul 2009 15:45:40 -0700 From: Ian Kelling User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ssh-host-config eval password bug References: <4A50EBA3 DOT 9090000 AT gmail DOT com> <4A51200A DOT 8090207 AT byu DOT net> In-Reply-To: <4A51200A.8090207@byu.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 Eric Blake wrote: > The eval is still reasonable, but with proper quoting: > > if eval cygrunsrv ... -y tcpip "${cygwin_env}" No, thats not true. It is impossible to safely eval arbitrary user input. Your simple quote doesn't help much: # x="ok;ls" # eval echo "{$x}" For more in depth information, read this: http://mywiki.wooledge.org/BashFAQ/048 - Ian Kelling -- 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