entrypoint: no link followed at the DMARC maps (audit I2)
Security audit 2026-10-17, finding I2 (= M4), stage 0. drop_links listed the outbound maps, sasldb2, the key tree and mail.log but not the three DMARC maps that postfix-config.sh creates as root with `[ -e ] || : >` when DMARC_REPORTS_ENABLE=true; -e is false for a dangling link and the redirect follows it, and /data/postfix is the panel's. Now the three are in drop_links, and both map loops refuse to create through a link (`[ -e ] || [ -L ] || : >`). e2e: TestStartsOnA28Data plants a dangling /data/postfix/dmarc_transport with DMARC reports on and expects the "removing the symbolic link" line, no file at the link's target, and a regular map. To be run on the server with the stage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -91,6 +91,7 @@ drop_links /data/dkim /data/dkim.new /data/opendkim /data/sasl /data/postfix /da
|
||||
/data/sasl/sasldb2 /data/postfix/queue \
|
||||
/data/postfix/sender_login_maps /data/postfix/relay_domains \
|
||||
/data/postfix/transport /data/postfix/relay_recipients /data/postfix/tls_policy \
|
||||
/data/postfix/dmarc_recipients /data/postfix/dmarc_transport /data/postfix/dmarc_relay_domains \
|
||||
/data/log/mail.log
|
||||
# Restored backups or previously-created state may contain panel-owned files
|
||||
# under /data; make sure they stay writable without disturbing anything that a
|
||||
|
||||
Reference in New Issue
Block a user