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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Cygwin Setup Command-line Arguments - Paths with a Space Incorrectly Parsed
References: <CAK0ZC5Uj8Z_uf_1nKUegt84Qn+OHiwsMVC_SO8AjFrrpUCQv1g@mail.gmail.com> <CA+Fg1xZFpb5uBbkP4KQxsZUvkjQETY4VjR0Y4k+Oe_D5DE0u9w@mail.gmail.com>
To: cygwin@cygwin.com
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Reply-To: Brian.Inglis@SystematicSw.ab.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: <CA+Fg1xZFpb5uBbkP4KQxsZUvkjQETY4VjR0Y4k+Oe_D5DE0u9w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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