[prev in list] [next in list] [prev in thread] [next in thread] 

List:       exim-users
Subject:    Re: [exim] router yields tainted data
From:       Niels_Kobschätzki_via_Exim-users <exim-users () exim ! org>
Date:       2021-04-28 0:14:30
Message-ID: BB42DBA1-94AB-490E-88C0-70E3C51D0758 () kobschaetzki ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

I found the problem. The server accessed the wrong configuration file because of a \
missing symlink.

Best

Niels

> On 28. Apr 2021, at 02:07, Niels Kobschätzki <niels@kobschaetzki.net> wrote:
> 
> Hi,
> 
> I have here a router which yields tainted data and I don‘t understand why - \
> especially since it works on some machines and not on others: 
> Log-output:
> 
> exim -v -bt test@domain.com
> 
> LOG: MAIN PANIC
> Tainted filename '/usr/local/etc/exim/redirects/domain.com'
> test@jobcenter-ge.de cannot be resolved at this time: dynamic_reroute router: \
> failed to expand "${readfile{/usr/local/etc/exim/redirects/$domain}{}}": failed to \
> open /usr/local/etc/exim/redirects/domain.com: Permission denied (euid=0 egid=9025) \
>  dynamic_reroute:
> driver = manualroute
> transport = remote_smtp
> domains = dsearch,ret=key;/usr/local/etc/exim/redirects
> route_list = * ${readfile{/usr/local/etc/exim/redirects/$domain_data}{}}
> 
> in the directory /use/local/etc/exit/redirects are files that look like \
> „domain.com" and contain just an ip-address. 
> Why is the data tainted? I use a dsearch with a return-value and $domain_data for \
> the route_list. So it should be de-tainted, shouldn‘t it? 
> Best,
> 
> Niels


["smime.p7s" (application/pkcs7-signature)]

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/


[prev in list] [next in list] [prev in thread] [next in thread]