Gnus development mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: larsi@gnus.org, eric@ericabrahamsen.net, emacs-devel@gnu.org,
	ding@gnus.org
Subject: Re: master ef14acf: Make nnml handle invalid non-ASCII headers more consistently
Date: Mon, 19 Dec 2022 19:44:02 +0200	[thread overview]
Message-ID: <83wn6ncmql.fsf@gnu.org> (raw)
In-Reply-To: <87k02nxq1e.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Mon, 19 Dec 2022 18:27:09 +0100)

> From: Florian Weimer <fweimer@redhat.com>
> Cc: larsi@gnus.org,  eric@ericabrahamsen.net,  emacs-devel@gnu.org,
>   ding@gnus.org
> Date: Mon, 19 Dec 2022 18:27:09 +0100
> 
> * Eli Zaretskii:
> 
> >> As I expected, I could reproduce the issue with new mail.  I'm happy to
> >> report that replacing nnml--encode-headers with your new version fixes
> >> the issue.
> >
> > Thanks, so I've now installed this on the emacs-29 branch, for the
> > upcoming Emacs 29.1.
> 
> It's a denial-of-service issue, so it should be backported to 28 if
> possible, too.

We don't plan on any more releases from the emacs-28 branch.  I guess
distros will do the backporting, though.

> >> I assume that there is some protection in place that tabs are not
> >> possible here?
> >
> > Tabs where, and what kind of protection are we talking about?
> 
> The .overview file is in tab-separated-values format, and I think the
> code is supposed to replace tabs with spaces before the lines are
> written.  But mail-encode-encoded-word-string/rfc2047-encode-string
> generally does not replace tabs, so your change shouldn't make things
> worse at least.

OK, thanks.


  reply	other threads:[~2022-12-19 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210122180801.14756.84264@vcs0.savannah.gnu.org>
     [not found] ` <20210122180802.F0A1E20A10@vcs0.savannah.gnu.org>
2022-12-16 22:42   ` Florian Weimer
2022-12-17  7:45     ` Eli Zaretskii
2022-12-17 14:57       ` Florian Weimer
2022-12-17 15:52         ` Eli Zaretskii
2022-12-19 13:59           ` Florian Weimer
2022-12-19 17:07             ` Eli Zaretskii
2022-12-19 17:27               ` Florian Weimer
2022-12-19 17:44                 ` Eli Zaretskii [this message]
2022-12-19 17:48               ` Eric Abrahamsen
2022-12-19 17:58                 ` Eli Zaretskii
2022-12-19 18:05                   ` Eric Abrahamsen
2022-12-19 18:16                     ` Eli Zaretskii

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=83wn6ncmql.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=fweimer@redhat.com \
    --cc=larsi@gnus.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.
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 NNTP newsgroup(s).