From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5102 invoked by alias); 13 Feb 2019 22:20:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 5022 invoked by uid 89); 13 Feb 2019 22:20:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=Repin, Andrey, andrey, repin X-HELO: forward103p.mail.yandex.net Received: from forward103p.mail.yandex.net (HELO forward103p.mail.yandex.net) (77.88.28.106) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Feb 2019 22:20:04 +0000 Received: from mxback3o.mail.yandex.net (mxback3o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::1d]) by forward103p.mail.yandex.net (Yandex) with ESMTP id BE7C318C02C4; Thu, 14 Feb 2019 01:20:01 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback3o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id DzSSwQ0W5P-K17qZLcD; Thu, 14 Feb 2019 01:20:01 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1550096401; bh=i6bTPBymNkwaLhTlAK5+hJZJRYXgyWrlSVs+OLHoumo=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=adw57PJukgLmAg/ZQ4IzrWw6OTbp6Hhb07+evHhPEpgoS86DmnXKvTX2xZ4pJvKXy /on9jC5WcfoRvb07IUT0LLWt3vL4yj+V5tzG0Q5MKHaweoSFNKM6bxPJGqnXWE9L0c 2WDz8G4tPumWzZEQe8P1FWOzNE1xS8RQQXHpbOeg= Authentication-Results: mxback3o.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 4mxtPXFOTS-K0Fua9vK; Thu, 14 Feb 2019 01:20:00 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Wed, 13 Feb 2019 22:09:47 -0000 Date: Wed, 13 Feb 2019 22:50:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <968457789.20190214010947@yandex.ru> To: Bill Stewart , cygwin@cygwin.com Subject: Re: sshd: computer name's case must match? In-Reply-To: References: <20190213103200.GK3718@calimero.vinschen.de> <20190213122509.GL3718@calimero.vinschen.de> <20190213161029.GY3718@calimero.vinschen.de> <20190213162614.GA3718@calimero.vinschen.de> <20190213175541.GE3718@calimero.vinschen.de> <20190213202537.GF3718@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00140.txt.bz2 Greetings, Bill Stewart! Preface: Please teach your mail agent to not quote raw email addresses. >> > (a) Domain or computer name portion to the left of the "+" must always >> > be uppercase >> >> No, the case must match the case of the domain or computername. >> >> > (b) Username after "+" sign (or username alone, without "+" sign) must >> > match case exactly >> > >> > Questions: >> > >> > 1. Are the above two statements (a) and (b) complete/correct? >> > >> > 2. With regards to (a), are there any cases where the domain or >> > computer name is not uppercase? >> >> Yes. In my domain I have four machines using all-lowercase machine >> name for no apparent reason. One is a Linux machine, one is a >> Windows 7 64 bit, the other two are Windows 8.1 32 and 64 bit machines. >> All others, including the Windows 8 machines, are all uppercase. > The computer or domain name case inconsistency would seem to be a > source of confusion, mainly because on the Windows side we are > case-retentive but not case-sensitive, and it is not immediately > obvious which case will apply in the case of a computer or domain > name. I can only add to what Corinna said previously: computer names may turn up having any letter casing, although I mostly observed Windows systems having all-uppercase names, if first letter was uppercase ("Station14" -> "STATION14"), where Linux systems would be case-exact. > According to: http://pubs.opengroup.org/onlinepubs/9699919799/ - >> 3.437 User Name - A string that is used to identify a user; >> see also User Database. To be portable across systems >> conforming to POSIX.1-2017, the value is composed of >> characters from the portable filename character set. The >> character should not be used as the first >> character of a portable user name. >> >> 3.282 Portable Filename Character Set >> >> The set of characters from which portable filenames are >> constructed. >> >> A B C D E F G H I J K L M N O P Q R S T U V W X Y Z >> a b c d e f g h i j k l m n o p q r s t u v w x y z >> 0 1 2 3 4 5 6 7 8 9 . _ - >> >> The last three characters are the , , >> and characters, respectively. > From this reference, it seems that a POSIX-compliant username cannot > contain the + character? > So my suggestion is for Cygwin to convert the name part before the + > automatically to upper (or lower) case. > Thoughts? -- With best regards, Andrey Repin Thursday, February 14, 2019 1:03:58 Sorry for my terrible english... -- 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