OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: /usr/lib/sasl2 failed to open directory

From: Mark Edwards (markantsclimbtree.com)
Date: Sat May 26 2007 - 23:00:12 CDT


On May 26, 2007, at 7:44 PM, Victor Duchovni wrote:

>> May 25 15:37:41 mini postfix/smtpd[4735]: looking for plugins in '/
>> usr/lib/sasl2', failed to open directory, error: No such file or
>> directory
>
> Neither symbolic links, nor hard links (which work, but create
> security
> issues) are the right answer. You must *copy* any required files into
> the chroot jail.

Copying the contents of /usr/lib/sasl2 into /var/spool/postfix/usr/
lib/sasl2/ results in errors such as:

May 26 20:52:50 mini postfix/trivial-rewrite[29635]: unable to
dlopen /usr/lib/sasl2/libsasldb.so.2: libdb-4.2.so: cannot open
shared object file: No such file or directory

Having a blank directory at /var/spool/postfix/usr/lib/sasl2/
resolves the issue as far as I can tell, so that's what I'm doing for
the time being. I'm not using cyrus-sasl so I don't care much about it.

I guess the question here is, how should this be resolved? It
appears that these errors would be generated on a default postfix
install on Debian or Ubuntu, since the cyrus-sasl stuff is a
dependency of the postfix .deb.

Do I need to file a Debian/Ubuntu bug report? Is it possible that
this is a misconfiguration on my end?

Thanks.

--
Mark Edwards