|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: trap decode to catch security attacks
From: Victor Duchovni (Victor.Duchovni
MorganStanley.com)
Date: Sat Dec 02 2006 - 13:44:38 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Dec 03, 2006 at 02:12:01AM +0800, Uwe Dippel wrote:
> I went through google and through the archives of postfix-users, but
> have yet to understand the consequences of this statement:
>
> # trap decode to catch security attacks
> decode: root
>
> This is default postfix, aliases. Now there are some people who say
> that's bad for security.
> The wording says it is a trap; some say it's dangerous (to have uucp at
> all). Should I remove that entry and keep the trap ? I am sure
> everything is there with a reason.
> Could someone point this out to me, please ?
This routes the mail to the system administrator, overrides any "decode"
alias in NIS or other sources that may be an actual pipe to "uudecode".
It does not run uudecode... If you don't have a "decode" user account,
and are not using NIS or other additional aliases(5) tables, you don't
need the decode alias, it is just another way of mailing "root" or
"postmaster", and adds no value in this case.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo
postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]