From: Lars Ingebrigtsen <larsi@gnus.org>
To: 26634@debbugs.gnu.org
Subject: bug#26634: [Lars Ingebrigtsen] Re: bug#26634: 26.0.50; The network security manager doesn't understand IDNA domains
Date: Sun, 22 Jul 2018 13:35:48 +0200 [thread overview]
Message-ID: <m3sh4bqz8r.fsf@gnus.org> (raw)
In-Reply-To: <m3tw5ev6p3.fsf@stories>
-------------------- Start of forwarded message --------------------
From: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: bug#26634: 26.0.50; The network security manager doesn't understand IDNA domains
Date: Sun, 22 Jul 2018 13:04:44 +0200
Ted Zlatanov <tzz@lifelogs.com> writes:
> Suggestion: what if we used IDNA and highlighting if multiple scripts
> are mixed in any segment of the DNS path (a "word" in the syntax)? And a
> tooltip explaining the problem? That would make it clear to the user.
You mean in the eww title bar? Yes, that would make sense...
> It would also be potentially beneficial in Dired and prog-mode. Here I
> would again flag any mixed scripts in a word.
Hm... well, the security implications of having a mixed-script file
name are different from mixed-script domain names.
> The same approach might be nice in `list-packages' in case someone
> malicious pushes out packages with confusables in the name. Here the
> check would flag anything non-ASCII.
That does sound useful.
> WDYT? A minor mode? Or maybe it exists already?
Not that I know of.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
-------------------- End of forwarded message --------------------
prev parent reply other threads:[~2018-07-22 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 3:13 bug#26634: 26.0.50; The network security manager doesn't understand IDNA domains Lars Ingebrigtsen
2018-04-13 13:18 ` Lars Ingebrigtsen
2018-04-13 14:44 ` Lars Ingebrigtsen
2018-04-13 15:03 ` Robert Pluim
2018-04-13 15:19 ` Lars Ingebrigtsen
2018-04-13 15:38 ` Robert Pluim
2018-04-15 13:58 ` Lars Ingebrigtsen
2018-07-22 11:35 ` Lars Ingebrigtsen [this message]
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=m3sh4bqz8r.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26634@debbugs.gnu.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).