Missing pam for cyrus sasl

Christopher Hunt huntc at internode.on.net
Tue Jul 31 04:50:12 PDT 2007


Just thought that I'd follow-up on this. The reason that I pam wasn't  
being built in was because it couldn't be found during build.  
Apparently the build for saslauthd looks for /usr/include/security.  
The following line overcomes the problem I was having:

	ln -s /usr/include/pam /usr/include/security

Regular ./configure and make then works.

Thanks to jklotz on the cyrus sasl list for pointing this one out.

Cheers,
-C

On 28/07/2007, at 7:56 AM, Christopher Hunt wrote:

> Hi Dan,
>
> Thanks for the response.
>
> I thought that it might be a build option but I couldn't find it.  
> I'll look harder.
>
> Thanks again.
>
> Cheers,
> -C
>
> On 28/07/2007, at 5:18 AM, Dan Shoop wrote:
>
>>
>> On Jul 26, 2007, at 8:41 AM, Christopher Hunt wrote:
>>
>>> Hi there,
>>>
>>> I'm trying to use cyrus sasl in conjunction with OS X's postfix  
>>> so that I can authenticate my smtp clients. I was wondering if  
>>> there were others on this list that have tried to do this given  
>>> that I'm getting a "unknown authentication mechanism: pam" on  
>>> issuing:
>>>
>>> ./saslauthd -a pam
>>>
>>> Any pointers? I don't think I've done anything abnormal - just  
>>> the standard configure, make and make install along with linking  
>>> the /usr/local/lib/sasl2 to /usr/lib/sasl2.
>>>
>>
>> AFAIK PAM is not included in the default build, you must specify  
>> you want to use it.


More information about the MacOSX-admin mailing list