From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#51733: 27.1; Detect impossible email addresses better Date: Mon, 17 Jan 2022 15:54:58 +0100 Message-ID: <87mtju76pp.fsf@gnus.org> References: <87czn8etuz.7.fsf@jidanni.org> <87tugkkfid.fsf@gnus.org> <83fss44rbn.fsf@gnu.org> <875yt0ipre.fsf@gnus.org> <834k8k3za3.fsf@gnu.org> <874k8jfloo.fsf@gnus.org> <83zgqb18hq.fsf@gnu.org> <87zgqb6tcm.fsf@gnus.org> <87tue3y96e.fsf@gnus.org> <83fspny8fp.fsf@gnu.org> <87pmory859.fsf@gnus.org> <83ee57y7xz.fsf@gnu.org> <87lezfy70y.fsf@gnus.org> <83czkry6jw.fsf@gnu.org> <87h7a3y5no.fsf@gnus.org> <87czkry3h8.fsf@gnus.org> <835yqjy26h.fsf@gnu.org> <878rveybyf.fsf@gnus.org> <49EACC4C-E21E-4123-A3D2-901958CF7DC4@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26364"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 51733@debbugs.gnu.org, jidanni@jidanni.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 17 16:28:46 2022 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 1n9Tw4-0006di-P9 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 17 Jan 2022 16:28:44 +0100 Original-Received: from localhost ([::1]:38892 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9Tw3-0000ji-RR for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 17 Jan 2022 10:28:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:34448) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9TQR-0000Z9-FC for bug-gnu-emacs@gnu.org; Mon, 17 Jan 2022 09:56:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54480) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n9TQR-0001KX-54 for bug-gnu-emacs@gnu.org; Mon, 17 Jan 2022 09:56:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n9TQQ-0008Aq-9p; Mon, 17 Jan 2022 09:56:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org, bugs@gnus.org Resent-Date: Mon, 17 Jan 2022 14:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51733 X-GNU-PR-Package: emacs,gnus Original-Received: via spool by 51733-submit@debbugs.gnu.org id=B51733.164243131429899 (code B ref 51733); Mon, 17 Jan 2022 14:56:02 +0000 Original-Received: (at 51733) by debbugs.gnu.org; 17 Jan 2022 14:55:14 +0000 Original-Received: from localhost ([127.0.0.1]:45875 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n9TPe-0007lx-0G for submit@debbugs.gnu.org; Mon, 17 Jan 2022 09:55:14 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:42612) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n9TPZ-0007gw-4p for 51733@debbugs.gnu.org; Mon, 17 Jan 2022 09:55:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=cruYPr7t2WQf/QjT4zIuBGk0SLxnp48h8A1zTOSxZJc=; b=PXR5b4OhSsXaclre00qi8wIdM4 UVbIbZ8trlPAm2NqSiNbbVDTp2Y4acnaW6FWD2YQc2dUv2XiGt5et/MrV0UhcKknURn4RhBu4V8Pt sDdzdMPOA0rA1javuSy987rXyjAT+dQl5KuCMACm7SQxLt8qv6eLL932f/h67aLpwQuM=; Original-Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9TPP-00019f-LI; Mon, 17 Jan 2022 15:55:02 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAMAAABg3Am1AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAM1BMVEX+/v7Q7fxtyPqj 3fvr9fkxsvzgtMPTUZ/h1czZlmTlrpfup3KviGSfbExeUD6yVz////+BBqVmAAAAAWJLR0QQlbIN LAAAAAd0SU1FB+YBEQ40O9mzfKwAAAFpSURBVEjHxZXRcoQgDEWNRDQS5P//tkkAdbvtBB+2vauA mAOXZJydps8LZpW2QS7RDA4AEAJggNDlbRFm61BWBgu2BgPKIpPhiDCD3NiApe60iJUgc6gDxZWf dTWUl0G9vAO2tr6sk3gBt4NdQMBzYqk+bzsA/AKgeXoHwg9AdYQoURZ4PwNM+AJABRB1XmZsUpqX MzRkXrR6dZFaND22OpCEWy5blnqFECTP0DrEWkyzVofaS0msLI1ozWnSUVzlF1dRjEPAasEWP7ZH jHGza3CDP9ZGe1e0dnOBlFJHZEQuwBeRElH2gHgcmRWROx8iL3GbRmXdhWzEriVd1YhsgGtJgWyu BGB5GAJy5p1YgOwDMTMzaaqIZMS+JTsvkVRARykNA2kUsCglngBU9RigR0AaBegE0hMgn57GAC7C lGeW2hHcDyjeMvpBgEvpmA8w6adWqmgMoNLjB4A9X4TZctP6XaN/Af+pL6x6Fsf3UPEvAAAAJXRF WHRkYXRlOmNyZWF0ZQAyMDIyLTAxLTE3VDE0OjUyOjU5KzAwOjAweh2gNAAAACV0RVh0ZGF0ZTpt b2RpZnkAMjAyMi0wMS0xN1QxNDo1Mjo1OSswMDowMAtAGIgAAAAASUVORK5CYII= X-Now-Playing: The Human League's _Dare_: "Seconds" In-Reply-To: <49EACC4C-E21E-4123-A3D2-901958CF7DC4@gnu.org> (Eli Zaretskii's message of "Mon, 17 Jan 2022 12:18:44 +0200") 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:224445 Archived-At: Eli Zaretskii writes: > Yes, I understand the general concern, but I'm asking how serious is > this in practice. Can you tell? I don't know how to quantity that. We're talking about security mechanisms, and they should be reliable. (But, yes, the differences are massive, especially in the Asian parts of the data.) >> In addition, that table assumes that each character belongs to a single >> script, which is also wrong. So I'm making a new table based on >> Scripts.txt and ScriptExtensions.txt. > > It is confusing to have 2 separate properties of a character that are > subtly incompatible, and for such obscure properties at that. It will > be source of many problems. So I think we should avoid that if it's > feasible. Can we plrase discuss any real problems that would be > xaused by using the existing char-table? It's impossible to implement the Unicode security recommendations based on the Blocks.txt data -- it's that simple. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no