-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Rspamd: improve DKIM key generation #3876
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.
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
Conversation
`rm` would fail when one of the files is not present, which is quite undesirable log (not harmful until `set -e` is introduced).
5c678a6 to
3b1d504
Compare
polarathene
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving since __do_as_rspamd_user() only appears to be relevant to the rspamd DKIM generation script.
We'd have avoided all this if permissions on the config volume weren't relevant correct? After the LDAP feature rework is done I'll fix up DKIM keypair generation for v15 too.
Absolutely! |
| [[ -f ${PUBLIC_KEY_FILE} ]] && rm "${PUBLIC_KEY_FILE}" | ||
| [[ -f ${PUBLIC_KEY_DNS_FILE} ]] && rm "${PUBLIC_KEY_DNS_FILE}" | ||
| [[ -f ${PRIVATE_KEY_FILE} ]] && rm "${PRIVATE_KEY_FILE}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe for a follow up "tuning":
rm -f "${PUBLIC_KEY_FILE}" etc. will always succeed, no matter if the file exist or not.
Description
Fixes #3873
Type of change
Checklist
docs/)CHANGELOG.md