X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=Kgt+6wMLHtCHIGeo AZTodwek8KExGoqzbFPrGLtu9NgbAMvuPqyLYVW2KqbS+VFbXN+0g49U6ttcG9Gy 3QSBPZrVaNkbrCNh5KGUdrn4c5eEjsjTR0UibLSZkBIPXE7Q5jVrMKXMfrPHzGx0 yNbdLiMRaNRAdzMeBz/iwBmPYAg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=bq5Y+xPvA+thjXDFKXYRAP 1fKz4=; b=w2KF7E66HNzBaomE6CjWpqdzP5wHHhLQ2nC/cKZ1YZiNTAHcgTu+yk NKj+I4VyWPmS/LrLatzXkWVV5kLVIlgGUbhD3pKLDCJ/lrPK5N5rGvZkgPM3FgC4 V2V4BIFMf65IbasBXdH5E89tjTpALRNcfinId3pXu/YYsuvT2ZnDs= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Z, Hx-spam-relays-external:64.59.136.139, H*RU:64.59.136.139, haase X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=abURpVgt c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=a1tCUh00tdhSlMhMKMoA:9 a=QEXdDO2ut3YA:10 Subject: Re: Cygwin Setup Command-line Arguments - Paths with a Space Incorrectly Parsed References: To: cygwin AT cygwin DOT com From: Brian Inglis Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Message-ID: <85fb010a-4fb5-1455-af6b-32e95048964c@SystematicSw.ab.ca> Date: Mon, 14 Nov 2016 12:23:43 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfGyjjM0lPgDBACV19gc/1kXVVU9Cx63zj968SypzFOxa3YChN63u1YPBYcashnOrU6FmPnTBo/M7Vs9nXOwPNbQYqOzaGFXZJsPnZM+tm7/vA1GbwvLe pQVZ5BjUPDVdvMIQt8EZ3v95Co7LN7wm3JStf9OekIqVuJ5QbuJNkxMOxZpkxs6CwnxPgl6pAgU4Zw== X-IsSubscribed: yes On 2016-11-14 07:43, Gerrit Haase wrote: > 2016-11-13 23:19 GMT+01:00 OwN-3m-All wrote: >> I'd like to automate Cygwin installation, but I don't want to rule >> out the possibility that a path with a space will not be used. > > You'll get a warning from Setup: it is strongly recommended, to use a > root path without spaces. I'd go further - it is strongly recommended that you use only a subset of printable ASCII characters to avoid problems with Windows OEM and NLS code pages, and Cygwin mapping of some characters to UTF-16 user defined supplementary characters, understood only by Cygwin internals, for POSIX compatibility. So disallow names with anything disallowed by Windows: "*/:<>?\| or outside the [!-~] range leaving [!#-)+-.0-9;=@-[\]-{}~] It would also be sensible to disallow anything interpreted by shells, including cmd, or programs, to avoid issues: !#$%&'();[]`{} reducing the set to [+-.0-9=@-Z^_a-z~] i.e. +,-.=@^_~ plus digits and letters, to maintain interoperability without issues. Leading -.@~ should be disallowed as they have special meaning, and trailing ~ is questionable as it is often used for backup files, removed by cleanup scripts, so you might also want to disallow these. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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