From: Andreas Schwab <schwab@linux-m68k.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
54624@debbugs.gnu.org, Aleksandr Vityazev <avityazev@posteo.org>
Subject: bug#54624: 29.0.50; textsec and ipv6 addresses
Date: Sun, 03 Apr 2022 18:58:34 +0200 [thread overview]
Message-ID: <87tuba3xz9.fsf@igel.home> (raw)
In-Reply-To: <C1FE4BCA-968C-486B-82FF-BE0F5A6053B4@acm.org> ("Mattias Engdegård"'s message of "Sun, 3 Apr 2022 18:53:05 +0200")
On Apr 03 2022, Mattias Engdegård wrote:
> Sorry, but these regexps aren't very precise, are they? They match a lot more than valid IP addresses. For example, both match "12345".
12345 is actually a valid IPv4 address, same as 0.0.48.57.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-04-03 16:58 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 [this message]
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=87tuba3xz9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=54624@debbugs.gnu.org \
--cc=avityazev@posteo.org \
--cc=larsi@gnus.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 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).