From: Stefan Kangas <stefan@marxist.se>
To: Gregory Heytings <gregory@heytings.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
47431@debbugs.gnu.org, hongyi.zhao@gmail.com
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Wed, 14 Apr 2021 09:55:09 -0500 [thread overview]
Message-ID: <CADwFkmmNBG+Jb3urVvX0ONHp_oeCwLj-vn_nrbCY2tcYGq7E_A@mail.gmail.com> (raw)
In-Reply-To: <6820a941ae99cf1eb9b0@heytings.org> (Gregory Heytings's message of "Wed, 31 Mar 2021 14:27:01 +0000")
Gregory Heytings <gregory@heytings.org> writes:
>>
>> I don't think there's an expectation of privacy here -- the user knows that
>> doing a whois query will result in server(s) being queried.
>>
>
> Okay.
>
>>
>> So I think whois.el should be rewritten to do the two step query (and be
>> asynchronous, which should be pretty trivial).
>>
>
> Okay, I'll do that.
I was completely unaware of this bug report, but I did some related work
here:
commit 5d456136169468e78c877ead2a3e279d9ebc7e4c
Author: Stefan Kangas <stefan@marxist.se>
Date: Wed Apr 7 13:35:59 2021 +0200
Update whois-server-tld
* lisp/net/net-utils.el (whois-server-tld): Update and add some
missing entries.
FWIW, I added a comment that argues in favour of the solution chosen
here. Even better that you have here checked it with IANA. Thanks for
working on this!
next prev parent reply other threads:[~2021-04-14 14:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 1:39 bug#47431: Process Whois connection broken by remote peer Hongyi Zhao
2021-03-27 6:30 ` Eli Zaretskii
2021-03-27 7:23 ` Gregory Heytings
2021-03-27 8:08 ` Eli Zaretskii
2021-03-27 11:01 ` Gregory Heytings
2021-03-27 11:04 ` Gregory Heytings
2021-03-28 15:39 ` Lars Ingebrigtsen
2021-03-28 20:23 ` Gregory Heytings
2021-03-29 0:19 ` Hongyi Zhao
2021-03-29 4:50 ` Eli Zaretskii
2021-03-29 7:35 ` Gregory Heytings
2021-03-29 8:38 ` Eli Zaretskii
2021-03-29 11:31 ` Gregory Heytings
2021-03-29 12:02 ` Eli Zaretskii
2021-03-29 12:12 ` Gregory Heytings
2021-03-29 14:16 ` Hongyi Zhao
2021-03-29 10:58 ` Lars Ingebrigtsen
2021-03-29 11:20 ` Gregory Heytings
2021-03-29 12:19 ` Gregory Heytings
2021-03-30 13:22 ` Lars Ingebrigtsen
2021-03-31 7:53 ` Gregory Heytings
2021-03-31 13:39 ` Lars Ingebrigtsen
2021-03-31 14:27 ` Gregory Heytings
2021-04-14 14:55 ` Stefan Kangas [this message]
2022-06-28 13:40 ` Lars Ingebrigtsen
2022-07-28 10:35 ` Lars Ingebrigtsen
2022-07-28 21:56 ` Gregory Heytings
2022-07-29 11:34 ` Lars Ingebrigtsen
2021-03-27 9:50 ` Hongyi Zhao
2021-03-27 9:57 ` Hongyi Zhao
2021-03-27 10:33 ` Eli Zaretskii
2021-03-27 12:29 ` Hongyi Zhao
2021-03-27 13:44 ` Eli Zaretskii
2021-03-28 1:41 ` Hongyi Zhao
2021-03-28 6:38 ` Eli Zaretskii
2021-03-28 7:12 ` Hongyi Zhao
2021-03-28 14:11 ` Lars Ingebrigtsen
2021-03-28 14:15 ` Eli Zaretskii
2021-03-28 14:19 ` Lars Ingebrigtsen
2021-03-28 14:55 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmNBG+Jb3urVvX0ONHp_oeCwLj-vn_nrbCY2tcYGq7E_A@mail.gmail.com \
--to=stefan@marxist.se \
--cc=47431@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=hongyi.zhao@gmail.com \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).