From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Hongyi Zhao Newsgroups: gmane.emacs.bugs Subject: bug#47431: Process Whois connection broken by remote peer. Date: Mon, 29 Mar 2021 08:19:05 +0800 Message-ID: References: <835z1dp0qg.fsf@gnu.org> <83y2e9nhne.fsf@gnu.org> <87zgynp9t5.fsf@gnus.org> <406246af7fb57420287b@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3671"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 47431@debbugs.gnu.org To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 29 02:20:10 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lQfda-0000oq-Ii for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 29 Mar 2021 02:20:10 +0200 Original-Received: from localhost ([::1]:49508 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lQfdY-0000X5-S4 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 28 Mar 2021 20:20:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42608) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lQfdS-0000Wx-6e for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 20:20:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35744) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lQfdR-0001qz-U7 for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 20:20:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lQfdR-0001i6-Ny for bug-gnu-emacs@gnu.org; Sun, 28 Mar 2021 20:20:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Hongyi Zhao Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 29 Mar 2021 00:20:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47431 X-GNU-PR-Package: emacs Original-Received: via spool by 47431-submit@debbugs.gnu.org id=B47431.16169771706532 (code B ref 47431); Mon, 29 Mar 2021 00:20:01 +0000 Original-Received: (at 47431) by debbugs.gnu.org; 29 Mar 2021 00:19:30 +0000 Original-Received: from localhost ([127.0.0.1]:47290 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQfcq-0001hB-F5 for submit@debbugs.gnu.org; Sun, 28 Mar 2021 20:19:30 -0400 Original-Received: from mail-yb1-f181.google.com ([209.85.219.181]:40599) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lQfcp-0001gy-18 for 47431@debbugs.gnu.org; Sun, 28 Mar 2021 20:19:23 -0400 Original-Received: by mail-yb1-f181.google.com with SMTP id a143so12004556ybg.7 for <47431@debbugs.gnu.org>; Sun, 28 Mar 2021 17:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KxETgrW2BcizqiYaX3S6mpjRnFk6kNDXQQ5cgHB0e9w=; b=eQT005Pc0vQP/uPvQmMZP3psknCN5YqpcC8oaEnVJeiykEucPVlaoo6Jj5REU7mwNY IVy3lbPIxaZ74nM9lUAd9yxfo6kwmUNgP2FPnbx5VkTFA1WyM9RC3cFiuU0y0NUN10uN 86KWo0Nk0ENJktyLQ6l755Fmi0EVOTjbJFf82zuSXb/5tSDJeZ7t541y9QHW8vy3PP9E Zfjswo5oxOlL/7wX4hBurtoZah5QE1ZXJv4Wipz3uHIwCp8Jssae0F1rO3n7fBBPtbsW VpvZHMBJWVWJ+g9pVpX17l9vSjpjvuseRwtH9m06YTxBXLoFY7y+Bxcjv9ZWm+NWgWPQ kAxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KxETgrW2BcizqiYaX3S6mpjRnFk6kNDXQQ5cgHB0e9w=; b=La0wWKDQBAFRcmiT7QsCPYekTkFBGJCjTu3i9I7CdZtroC+sANkzlM/zK9w0d/08z9 rCSsLTy+Y7kK+ylyBi6EjPm/J9RI+q6egTludS3/EsHhOaYPIra/DyysJwEJN5oQtw2X ids17sqlpoKAyghLG5g+J3Q1oen731Y1NTVMYClhbbqHbDYAl4+YJdxP8EaTV2Kxu3z1 YbJZRZJAo/VYijE+zNjhv5R7otr5Co1z/wOb7WMj56zYhd2jH/tZtVn/JJw5Tr1eKg8u 4WqEKfrwR+hxy5Mw+EykmwfHUAym9xaBBTE5KUz40Z26HU4fmvJ6wBqC3b65I8ukbQfc L3OQ== X-Gm-Message-State: AOAM530xtxUuxgt9aLvn1Q0f5X6LyesNBK4NyLjN/rXmsve7qsc5w+Lx v52POXlXMLlSrcbjMltzhVB7hBgJWHDctaw0n1894HbjF1N6RPvj X-Google-Smtp-Source: ABdhPJw9xCj5ovIE9lJsQeea0gfcgvQqLgurCmvZkE7EjXezzLYTCuJmZAdu4eXsqLAPaKHzXnTwysxWttkK6sRiBuQ= X-Received: by 2002:a25:d8ce:: with SMTP id p197mr34768555ybg.119.1616977157445; Sun, 28 Mar 2021 17:19:17 -0700 (PDT) In-Reply-To: <406246af7fb57420287b@heytings.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:203216 Archived-At: On Mon, Mar 29, 2021 at 4:23 AM Gregory Heytings wrote: > > > >> [2] https://raw.githubusercontent.com/rfc1036/whois/next/tld_serv_list > > > > The list originates at whois.iana.org... which is a server that seems > > to respond to whois queries nicely. So we could just update > > whois-server-name to that? And remove whois-server-tld. > > > > That would be ideal/simpler, but whois.iana.org only contains information > about the whois server to use for each TLD. For instance whois -h > whois.iana.org gnu.org tells you that the whois server to contact is > whois.pir.org. IOW, without a built-in list, each whois query would > create two requests, one to whois.iana.org, and one to the actual whois > server. IOW again, a whois request would become: > > whois -h $(whois -h whois.iana.org DOMAIN | grep '^whois:' | cut -d: -f2) DOMAIN > > Would that be acceptable? The suggested method really can do the trick: ;;; begin quote $ whois -h $(whois -h whois.iana.org facebook.com | grep '^whois:' | cut -d: -f2) facebook.com Domain Name: FACEBOOK.COM Registry Domain ID: 2320948_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.registrarsafe.com Registrar URL: http://www.registrarsafe.com Updated Date: 2020-03-10T18:53:59Z Creation Date: 1997-03-29T05:00:00Z Registry Expiry Date: 2028-03-30T04:00:00Z Registrar: RegistrarSafe, LLC Registrar IANA ID: 3237 Registrar Abuse Contact Email: abusecomplaints@registrarsafe.com Registrar Abuse Contact Phone: +1-650-308-7004 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited Name Server: A.NS.FACEBOOK.COM Name Server: B.NS.FACEBOOK.COM Name Server: C.NS.FACEBOOK.COM Name Server: D.NS.FACEBOOK.COM DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of whois database: 2021-03-29T00:14:06Z <<< For more information on Whois status codes, please visit https://icann.org/epp NOTICE: The expiration date displayed in this record is the date the registrar's sponsorship of the domain name registration in the registry is currently set to expire. This date does not necessarily reflect the expiration date of the domain name registrant's agreement with the sponsoring registrar. Users may consult the sponsoring registrar's Whois database to view the registrar's reported date of expiration for this registration. TERMS OF USE: You are not authorized to access or query our Whois database through the use of electronic processes that are high-volume and automated except as reasonably necessary to register domain names or modify existing registrations; the Data in VeriSign Global Registry Services' ("VeriSign") Whois database is provided by VeriSign for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. VeriSign does not guarantee its accuracy. By submitting a Whois query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to VeriSign (or its computer systems). The compilation, repackaging, dissemination or other use of this Data is expressly prohibited without the prior written consent of VeriSign. You agree not to use electronic processes that are automated and high-volume to access or query the Whois database except as reasonably necessary to register domain names or modify existing registrations. VeriSign reserves the right to restrict your access to the Whois database in its sole discretion to ensure operational stability. VeriSign may restrict or terminate your access to the Whois database for failure to abide by these terms of use. VeriSign reserves the right to modify these terms at any time. The Registry database contains ONLY .COM, .NET, .EDU domains and Registrars. ;;; end quote But I'm not sure if this is the standard query procedures suggested/defined by the whois protocol itself. Regards -- Assoc. Prof. Hongyi Zhao Theory and Simulation of Materials Hebei Polytechnic University of Science and Technology engineering NO. 552 North Gangtie Road, Xingtai, China