From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 482941F670 for ; Thu, 14 Oct 2021 11:44:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231190AbhJNLqE (ORCPT ); Thu, 14 Oct 2021 07:46:04 -0400 Received: from smtp.hosts.co.uk ([85.233.160.19]:11438 "EHLO smtp.hosts.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229984AbhJNLqD (ORCPT ); Thu, 14 Oct 2021 07:46:03 -0400 Received: from host-84-13-154-214.opaltelecom.net ([84.13.154.214] helo=[192.168.1.37]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1maz9R-0006Fx-9p; Thu, 14 Oct 2021 12:43:57 +0100 Subject: Re: [BUG] credential wildcard does not match hostnames containing an underscore To: Alex Waite , Aaron Schrab , "brian m. carlson" , Jeff King , Junio C Hamano , git@vger.kernel.org References: <28ff3572-1819-4e27-a46d-358eddd46e45@www.fastmail.com> From: Philip Oakley Message-ID: <6ea198bf-6013-6cdf-3e56-7574975b1d7a@iee.email> Date: Thu, 14 Oct 2021 12:43:55 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-GB Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 13/10/2021 17:21, Alex Waite wrote: > In my view, the primary bug is how difficult it was to debug what was going wrong. This is most easily solved by improving the git docs to specify which characters will be matched. Even better if GIT_TRACE (or something similar) can inform/warn the user about matching. It did sound to me that the documentation route was a way out of the confusing situation. -- Philip