From: Lars Ingebrigtsen <larsi@gnus.org>
To: Aleksandr Vityazev <avityazev@posteo.org>
Cc: 54624@debbugs.gnu.org
Subject: bug#54624: 29.0.50; textsec and ipv6 addresses
Date: Tue, 29 Mar 2022 17:12:13 +0200 [thread overview]
Message-ID: <87bkxoaj3m.fsf@gnus.org> (raw)
In-Reply-To: <874k3hlyvj.fsf@posteo.org> (Aleksandr Vityazev's message of "Tue, 29 Mar 2022 12:36:00 +0000")
Aleksandr Vityazev <avityazev@posteo.org> writes:
> #+begin_src elisp
> (textsec-domain-suspicious-p "21a:34aa:c782:3ad2:1bf8:73f8:141:66e8")
> => "Disallowed character: : (#x3a, COLON)"
> (textsec-domain-suspicious-p "[21a:34aa:c782:3ad2:1bf8:73f8:141:66e8]")
> => "Disallowed character: [ (#x5b, LEFT SQUARE BRACKET)"
> #+end_src
>
> I think it is not entirely correct. It may be possible to add additional
> validation for such addresses in the textsec-domain-suspicious-p function.
> WDYT?
Yup; I've now done so in Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-29 15:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 12:36 bug#54624: 29.0.50; textsec and ipv6 addresses Aleksandr Vityazev
2022-03-29 15:12 ` Lars Ingebrigtsen [this message]
2022-04-03 16:53 ` Mattias Engdegård
2022-04-03 16:58 ` Andreas Schwab
2022-04-03 17:04 ` Mattias Engdegård
2022-04-03 17:07 ` Lars Ingebrigtsen
2022-04-03 17:09 ` Lars Ingebrigtsen
2022-04-03 17:02 ` Lars Ingebrigtsen
2022-04-03 17:16 ` Mattias Engdegård
2022-04-03 17:49 ` Andreas Schwab
2022-04-04 10:42 ` Lars Ingebrigtsen
2022-04-04 12:48 ` Mattias Engdegård
2022-04-04 13:33 ` Robert Pluim
2022-04-06 9:19 ` Lars Ingebrigtsen
2022-04-06 13:28 ` Mattias Engdegård
2022-04-07 11:04 ` Lars Ingebrigtsen
2022-04-07 17:18 ` Mattias Engdegård
2022-04-07 22:13 ` Andreas Schwab
2022-04-08 9:08 ` Mattias Engdegård
2022-04-08 9:18 ` Andreas Schwab
2022-04-08 9:25 ` Mattias Engdegård
2022-04-11 14:29 ` Mattias Engdegård
2022-04-11 15:34 ` 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=87bkxoaj3m.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54624@debbugs.gnu.org \
--cc=avityazev@posteo.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).