MESSAGE
| DATE | 2015-03-17 |
| FROM | Rick Moen
|
| SUBJECT | Re: [NYLXS - HANGOUT] cable crimping
|
Quoting Chris Knadle (Chris.Knadle-at-coredump.us):
> If you look at the mailman_transport, that's a pipe transport.
Certainly I've actually never (before) looked into the guts of the
recommended router or transport definitions. The main functional
advantage of using that system was, frankly, freeing one's self from
having to continually futz around manually adding and removing
/etc/aliases lines, and instead let the MLM mailing list definition
files get accessed by the MTA directly.
That having been said, we can at least hope in this case that the MTA
does careful input validation on what gets sent through
mailman_transport's pipe driver. The regex disassembly that derives the
local part string looks competent, for example.
Anyway, thanks for pointing that out. Learned something.
> This is the case by default, but not if you set the user and group in
> the transport (such as they did in the Mailman example). Furthermore
> if you look in section 29 concerning the pipe transport, there's an
> allow_commands option to limit what commands a transport can call.
Yeah, this is what one hopes to see.
> At least with Exim using a pipe via /etc/aliases doesn't /have/ to be
> something terribly insecure. You do need to know what you're doing...
> sure.
I never said I had anything inherently against pipes, mind you. This is
Unix, after all. ;->
|
|
