From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 54624@debbugs.gnu.org, Aleksandr Vityazev <avityazev@posteo.org>
Subject: bug#54624: 29.0.50; textsec and ipv6 addresses
Date: Mon, 04 Apr 2022 12:42:54 +0200 [thread overview]
Message-ID: <87czhxgmdt.fsf@gnus.org> (raw)
In-Reply-To: <13DB0609-9BEB-42E5-BF2E-B29638A7F3E1@acm.org> ("Mattias Engdegård"'s message of "Sun, 3 Apr 2022 19:16:25 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
> Would you mind if I removed some ambiguity from the regexps then?
> Maybe even simplifying them to "[0-9.]+" and "[0-9a-f:]+"
> respectively?
Fine by me, but addresses that are too long should be suspicious (to
catch people obfuscating by doing things like 000000000000000127.0.0.1
and similar). That's what I was intending to catch with the {} things
without having to actually do the hard maths myself. :-)
And as Andreas said, I had forgotten that IPv6 addresses can contain
dots, so if you could fix that at the same time...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-04 10:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czhxgmdt.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54624@debbugs.gnu.org \
--cc=avityazev@posteo.org \
--cc=mattiase@acm.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.