From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 97851 invoked by alias); 13 Feb 2019 01:35:07 -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 97841 invoked by uid 89); 13 Feb 2019 01:35:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=BAYES_40,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=authority, stewart, Stewart, H*UA:Bat! X-HELO: forward100j.mail.yandex.net Received: from forward100j.mail.yandex.net (HELO forward100j.mail.yandex.net) (5.45.198.240) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Feb 2019 01:35:04 +0000 Received: from mxback23g.mail.yandex.net (mxback23g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:323]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 34B5C50E0FC5; Wed, 13 Feb 2019 04:35:02 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback23g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id PNgsQxWHX1-Z2Y0lqPQ; Wed, 13 Feb 2019 04:35:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1550021702; bh=Zc745xhMpQ9Joa8I+rCZ4xJX5xXWcknGsNaPZIPlQH4=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=nfwxJAXhhIuj2FKweRRr8vlwIVv3rszQ+/iIT5QZuNNdBYxbluPLIfhSkmpgA9SL6 Ic9dtxTXpWJC/warclkXnfLydRDJNbKseB+Y9zNlIaDQJlx1tam5DdnT0xlGcdLOl9 cINQXU9c4mfvVqEiQ8vSnG4pqTTDECpck5W6wgAw= Authentication-Results: mxback23g.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id xHEw1J7RPn-Z1Oq0WPg; Wed, 13 Feb 2019 04:35:01 +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 01:20:56 -0000 Date: Wed, 13 Feb 2019 01:35:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <627225163.20190213042056@yandex.ru> To: Bill Stewart , cygwin@cygwin.com Subject: Re: sshd: computer name's case must match? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00110.txt.bz2 Greetings, Bill Stewart! > I am testing sshd using the cygwin1.dll 3.x version (run as SYSTEM - > S4U logon - works great!). > One thing I've noticed is that if I use ssh log onto a remote > domain-joined machine (e.g., connect with COMPUTER+localname), the > 'COMPUTER' prefix must be uppercase - if I specify > 'computer+LocalName', the user is unknown. > This doesn't seem to be the case if I change the username's case - > 'COMPUTER+localname' also works. > Is this by design or by accident? With no authority on the matter I would say that it follows Kerberos domain names which are written in capital letters. -- With best regards, Andrey Repin Wednesday, February 13, 2019 4:19:00 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