GNU bug report logs - #51733
27.1; Detect impossible email addresses better

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51733 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: bug#51733: 27.1; Detect impossible email addresses better
Date: Mon, 17 Jan 2022 18:47:09 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: 51733 <at> debbugs.gnu.org,  jidanni <at> jidanni.org
> Date: Mon, 17 Jan 2022 15:54:58 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> 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.

Well, now that I know the answer, I don't think it's hard to quantify.
But maybe I'm missing something.

> (But, yes, the differences are massive, especially in the Asian parts of
> the data.)

I don't think I understand what you mean by "the Asian parts".  Do you
mean the CJK parts where we lump several scripts together into 'han'
and 'kana'?

> It's impossible to implement the Unicode security recommendations based
> on the Blocks.txt data -- it's that simple.

Can you tell more about why it is impossible?  If it's a relatively
simple issue of "translating" the Unicode script names into ours, then
it should be quite simple.  Since you say it's impossible, I guess
there's some factor(s) here that I miss?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.