[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cyrus-sasl
Subject:    Re: cyrus-sasl and plugin's dirertory
From:       Sergey via Cyrus-sasl <cyrus-sasl () lists ! andrew ! cmu ! edu>
Date:       2016-07-04 19:29:43
Message-ID: 201607042329.43527.a_s_y () sama ! ru
[Download RAW message or body]

On Friday 01 July 2016, Dan White wrote:

> >> The plugin path is hard coded within the sasl glue library
> >> (libsasl2),

> >Is there a way to get this hard coded path inside application ?
 
> What are you trying to accomplish?

I don't know at this time. I want to try to understand Debian's patch.

A patch with hard override sasl_getconfpath_t used in Debian now. Hard
definition for sasl_getpath_t was used some years ago also (but not now).
It was needed probably.

The http://http.debian.net/debian/pool/main/p/postfix/postfix_2.11.3-1.diff.gz
contains
postfix-2.11.3/src/xsasl/xsasl_cyrus_common.h.diff
postfix-2.11.3/src/xsasl/xsasl_cyrus_log.c.diff
postfix-2.11.3/src/xsasl/xsasl_cyrus_client.c.diff
postfix-2.11.3/src/xsasl/xsasl_cyrus_server.c.diff

xsasl_getpath() defined but not used
xsasl_getconfpath() used for client and server

Right ? 

I seems to add hard coded path from sasl is a good idea. If it's really necessary
of course.

BTW. Accrording sasl_callbacks(3) sasl_getconfpath_t should be used for server
only and xsasl_cyrus_client.c.diff isn't needed. Right ?

-- 
Regards,
Sergey
[prev in list] [next in list] [prev in thread] [next in thread]