From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master ce63f91025: Add textsec functions for verifying email addresses
Date: Sat, 22 Jan 2022 12:01:10 +0200 [thread overview]
Message-ID: <83zgnom6mx.fsf@gnu.org> (raw)
In-Reply-To: <87r1921snz.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 20 Jan 2022 13:46:24 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com, emacs-devel@gnu.org
> Date: Thu, 20 Jan 2022 13:46:24 +0100
>
> > We could try appending some representative text to the string being
> > tested, of course. For example, append a fixed string like this:
> >
> > a1א:!
> >
> > and see if the function returns non-nil position that points to one of
> > those characters; if so, consider the original string "unsafe".
> >
> > Would that be good enough for textsec purposes?
>
> Sounds good to me. It should probably be baked into its own utility
> function, so that other people that wonder about strings they have
> doesn't have to know anything about these things.
Now done, see the new function textsec-bidi-controls-suspicious-p.
Feel free to tweak as needed, if the API is not convenient.
next prev parent reply other threads:[~2022-01-22 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164250841214.433.17670666873471731764@vcs2.savannah.gnu.org>
[not found] ` <20220118122012.7A3A4C0DA1B@vcs2.savannah.gnu.org>
2022-01-18 13:30 ` master ce63f91025: Add textsec functions for verifying email addresses Po Lu
2022-01-18 18:42 ` Eli Zaretskii
2022-01-20 8:47 ` Lars Ingebrigtsen
2022-01-20 9:40 ` Eli Zaretskii
2022-01-20 9:49 ` Lars Ingebrigtsen
2022-01-20 10:20 ` Eli Zaretskii
2022-01-20 11:08 ` Lars Ingebrigtsen
2022-01-20 11:29 ` Eli Zaretskii
2022-01-20 12:46 ` Lars Ingebrigtsen
2022-01-22 10:01 ` Eli Zaretskii [this message]
2022-01-22 11:25 ` Lars Ingebrigtsen
2022-01-20 8:49 ` Lars Ingebrigtsen
2022-01-20 10:04 ` Eli Zaretskii
2022-01-20 10:07 ` Lars Ingebrigtsen
2022-01-18 13:38 ` Robert Pluim
2022-01-19 14:37 ` Lars Ingebrigtsen
2022-01-19 14:49 ` Robert Pluim
2022-01-19 14:54 ` 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=83zgnom6mx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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).