Hi Markus,

On Fri 31/Mar/2017 09:36:27 +0200 Markus Wanner wrote:
> On 03/31/2017 12:26 AM, Sam Varshavchik wrote:
>> libcourierauthcommon is not solely an externally-linked library. It's
>> also linked to by other .so-s in the package. These symbols correspond
>> to internal APIs.
> Am I correct to assume that libcourierauthcommon is an internal library
> and not part of the public API of courier-auth, i.e. users of
> courier-auth shouldn't ever directly link to it?
> Do libauthpam.so and libauthcustom.so exposed a public API?

I, for one, run my own pipeauth

ldd /etc/courier/authlib/authProg
        linux-vdso.so.1 =>  (0x00007fffb59bc000)
        libcourierauthsasl.so => 
/usr/local/lib/courier-authlib/libcourierauthsasl.so (0x00007ff1e44cd000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff1e4140000)
        libcourierauthcommon.so => 
/usr/local/lib/courier-authlib/libcourierauthcommon.so (0x00007ff1e3f37000)
        libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so 
        /lib64/ld-linux-x86-64.so.2 (0x00007ff1e46d0000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff1e37a1000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 

API recently changed, so my authProg is now portable, but I haven't autoconfed 
it yet.

Attachment: signature.asc
Description: OpenPGP digital signature

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
courier-users mailing list
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to