https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #9 from Simon Arlott ---
(In reply to Jeremy Harris from comment #8)
> Perhaps we should add new options for the client side of the plaintext
> authenticator (say, "client_send_1", "client_send_2").
> Define them as just (expanded) string,
https://bugs.exim.org/show_bug.cgi?id=2687
Jasen Betts changed:
What|Removed |Added
CC||ja...@treshna.com
--- Comment #10 from Jasen
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #13 from Simon Arlott ---
I've just realised that there is a much simpler solution to this problem:
Exim supports multiple lines in strings/lists/expansions/etc.
RFC 2595 does not allow CR or LF in any of the response values, because they
https://bugs.exim.org/show_bug.cgi?id=2820
Bug ID: 2820
Summary: out-of-bounds read
Product: Exim
Version: 4.96
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #12 from Simon Arlott ---
(In reply to Jasen Betts from comment #10)
> wouldn't changing to a list just move the problem to quoting trailing and
> leading whitespace?
The existing "client_send" is already a list. You must quote whitespace
https://bugs.exim.org/show_bug.cgi?id=2687
--- Comment #11 from Jeremy Harris ---
To be fair, you have to quote the current to handle a trailing space. At least
moving to a list per comment 9 makes such quoting needs the same as all lists.
I'm unclear where you're getting $item from in your
