Skip to content

dkim: enforce 0600 on private keys at every start #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MarvAmBass merged 1 commit into from
Sep 28, 2026
Merged

dkim: enforce 0600 on private keys at every start #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions scripts/entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,6 +360,18 @@ fi
rm -rf /tmp/tls 2> /dev/null
cp -a /etc/postfix/tls /tmp/tls

##
# DKIM key permissions — every start
##
# opendkim refuses keys that group/others can read ("key data is not secure")
# and then tempfails every message of that domain (4.7.1). The keys live on a
# volume, so their mode is whatever the host left; enforce it on each start
# (after init, so freshly generated keys are covered too).
if [ -d /etc/postfix/additional/opendkim/keys ]; then
echo ">> DKIM - enforce key permissions (default.private -> 0600)"
find /etc/postfix/additional/opendkim/keys -name default.private ! -perm 0600 -print -exec chmod 0600 {} +
fi

##
# CMD
##
Expand Down
Loading