-
Notifications
You must be signed in to change notification settings - Fork 100
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
Use alias wrapper only if it is really needed #946
Comments
I also think the following condition in Sympa::Aliases::Template is not a good design pattern for a two step process (update alias file, newaliases program).
My suggestion would be to have one configuration parameter for each task. |
See also #1009 |
I suggest we should cataloguing in which cases we really need to use the wrapper. For most cases we can probably recommend to use configure flags |
Also now with the environment cleaned out in the alias wrapper we have the detrimental effect that SYMPALIB is not passed on. Thus sympa_newaliases.pl fails in a cpanm/locallib setup as the script doesn't find the needed Perl modules. But we don't need the wrapper for Postfix or Exim if the permissions are set up correctly. |
This allows you to invoke the command from "sendmail_aliases" without using the wrapper (sympa-community#946).
This allows you to invoke the command from "sendmail_aliases" without using the wrapper (sympa-community#946).
This is a follow up to #943. It is established security practice to only elevate privileges if really needed. Currently we always call the wrapper instead of the newaliases program, which is a bad idea.
Especially as the wrapper is usually not needed. With postfix you are usually running postmap. Exim can use plain text files, so it doesn't need any newaliases program.
So we could call the program directly (at least in the default configuration).
Does that make sense?
The text was updated successfully, but these errors were encountered: