Re: [courier-users] courier-authlib: exported symbols
Hello Alessandro, On 03/31/2017 10:49 AM, Alessandro Vesely wrote: > I, for one, run my own pipeauth > > ldd /etc/courier/authlib/authProg > linux-vdso.so.1 => (0x7fffb59bc000) > libcourierauthsasl.so => > /usr/local/lib/courier-authlib/libcourierauthsasl.so (0x7ff1e44cd000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff1e414) > libcourierauthcommon.so => > /usr/local/lib/courier-authlib/libcourierauthcommon.so (0x7ff1e3f37000) > libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so > (0x7ff1e3d2a000) > /lib64/ld-linux-x86-64.so.2 (0x7ff1e46d) > libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x7ff1e3a23000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff1e37a1000) > libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x7ff1e358b000) > libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 > (0x7ff1e3354000) The interesting question here would be whether you're linking against libcourierauthsasl (and using its symbols only) or if your authProg depends on libcourierauthcommon, directly. (Indirectly, via libcourierauthsasl, libcourierauthcommon will always be linked in either case.) (Other than that I note that you're not using Debian packages, in the first place, so you wouldn't be affected. I still appreciate your inputs. Maybe there are Debian users doing or wanting to do the same.) Kind Regards Markus Wanner 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 courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
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 => (0x7fffb59bc000) libcourierauthsasl.so => /usr/local/lib/courier-authlib/libcourierauthsasl.so (0x7ff1e44cd000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff1e414) libcourierauthcommon.so => /usr/local/lib/courier-authlib/libcourierauthcommon.so (0x7ff1e3f37000) libcourierauth.so => /usr/local/lib/courier-authlib/libcourierauth.so (0x7ff1e3d2a000) /lib64/ld-linux-x86-64.so.2 (0x7ff1e46d) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7ff1e3a23000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff1e37a1000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7ff1e358b000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x7ff1e3354000) API recently changed, so my authProg is now portable, but I haven't autoconfed it yet. Ale 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 courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Sam, 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? Kind Regards Markus Wanner 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 courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courier-authlib: exported symbols
Markus Wanner writes: Hello Sam, I'm about to take over maintenance of the courier-mta packages in Debian, so I'll likely have further questions. Let's start with a simple one regarding courier-authlib: Compared to 0.66.4, these three symbols have vanished from libcourierauthcommon.so.0 in version 0.67.0: * auth_parse_chpass_clause@Base 0.66.4 * auth_parse_select_clause@Base 0.66.4 * authgetconfig@Base 0.66.4 What happened to them? Removing symbols is certain to be backwards-incompatible, but the library's soversion didn't change. If the authlib is intended to be backwards-incompatible, mind to incement the soversion? In addition, these methods were added: > (c++)"courier::auth::config_file::expand_string(std::__cxx11::basic_string
