Alessandro Vesely writes:
Hi all,while reviewing my Courier installation, I stumbled upon how my authProg.c is compiled. It uses -I/my/path/to/auth/cur -L/usr/path/to/courier-authlib and -lcourierauthsasl, on a server with courier-authlib-0.66.4.20160106. On a stock Debian jessie (0.66.1) I have to add two more libraries. The main difficulty is to get the sources for the include files:I include courierauth.h and courierauthsasl.h from authlib-devel. But I also need:#include "libs/libhmac/hmac.h" // for struct hmac_hashinfo #include "cramlib.h" // for auth_cram_callback In addition, I also need auth.h, because cramlib.h includes it (it wouldsuffice to declare "struct authinfo;" to avoid the inclusion). All file namesin include_HEADER start with "courier", so some renaming would be in order if this issue is ever addressed.I don't think I'm going to switch to binary versions of Courier any time soon, so I don't really need a cleaner compiling environment for authpipe. However,since a courier-authlib-dev package exists, I wonder why it doesn't support SASL. I use authsasl_frombase64, auth_cram_callback, and hmac_list. What do everybody else do?
It should be possible for you to support SASL authentication by using authsasl_list, that's declared in courierauthsasl.h. You shouldn't need to look at the lower-level functions.
pgpai6QTTRanb.pgp
Description: PGP 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
