From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [News item review] Exim >=4.94 transports: tainted not permitted
Date: Thu, 06 May 2021 15:01:33 +0200 [thread overview]
Message-ID: <6358100.FjKLVJYuhi@pinacolada> (raw)
In-Reply-To: <YI53UognwjnWa6g1@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
Am Sonntag, 2. Mai 2021, 11:56:34 CEST schrieb Fabian Groffen:
> Title: Exim >=4.94 disallows tainted variables in transport
> configurations Author: Fabian Groffen <grobian@gentoo.org>
> Posted: 2021-05-??
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed: mail-mta/exim
>
> Since the release of Exim-4.94, transports refuse to use tainted
> data in constructing a delivery location. If you use this in your
> transports, your configuration will break, causing errors and
> possible downtime.
>
> Particularly, the use of $local_part in any transport, should likely
> be updated with $local_part_data. Check your local_delivery
> transport, which historically used $local_part.
>
> Unfortunately there is not much documentation on "tainted" data for
> Exim[1], and to resolve this, non-official sources need to be used,
> such as [2] and [3].
This is a safety mechanism that is part of Perl (essentially a way of
tracking data that is derived from "insecure" sources).
So it probably would make sense to at least point towards that concept
in Perl.
https://perldoc.perl.org/perlsec
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2021-05-06 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 9:56 [gentoo-dev] [News item review] Exim >=4.94 transports: tainted not permitted Fabian Groffen
2021-05-02 10:23 ` Ulrich Mueller
2021-05-02 10:42 ` Fabian Groffen
2021-05-06 13:01 ` Andreas K. Huettel [this message]
2021-05-06 13:07 ` Fabian Groffen
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=6358100.FjKLVJYuhi@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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