[ARGUS] sasl a solution (ugly, but a solution :-))
Peter Van Epp
vanepp at sfu.ca
Mon Aug 16 11:38:40 EDT 2004
Thats the conclusion I came to as well (especially since 1.5.28
seg faults, although that may be because maxbuffersize isn't set). I converted
the client side to 2.1.19 yesterday and now for server (as well as trying
maxbuffer size on 1.5.28 which is easier :-)) ...
Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada
On Mon, Aug 16, 2004 at 11:14:52AM -0400, Carter Bullard wrote:
> Hey Peter,
> we should target sasl-2.x, and try to be compatible
> with sasl-1.x but 2.x has been out for a while.
>
> Carter
>
>
> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu
> [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of Peter Van Epp
> Sent: Saturday, August 14, 2004 1:43 AM
> To: argus-info at lists.andrew.cmu.edu
> Subject: Re: [ARGUS] sasl a solution (ugly, but a solution :-))
>
> OK, by that fine method "monkey see, monkey do" I have an aclocal.m4
> and several Makefile.in patches that will find sasl 2.1.19 which appears to
> be
> the latest version as installed from the tar ball. However it looks like
> there
> was a major version change for a reason :-)
>
> making in ./common
> gcc -O2 -I. -I../include -I/usr/local/include/sasl -DPACKAGE_NAME=\"\"
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\"
> -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_UNISTD_H=1 -DARGUS_SASL=1
> -DHAVE_SYS_SOCKIO_H=1 -DHAVE_STRING_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_FILE_H=1
> -DHAVE_SYSLOG_H=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_STRERROR=1 -DSTDC_HEADERS=1
> -c ./argus_parse.c
> ./argus_parse.c: In function `ArgusWriteConnection':
> ./argus_parse.c:2060: warning: passing arg 4 of `sasl_encode' from
> incompatible pointer type
> In file included from ./argus_parse.c:2198:
> ../include/saslint.h: At top level:
> ../include/saslint.h:109: syntax error before `sasl_external_properties_t'
> ./argus_parse.c: In function `ArgusReadSaslStreamSocket':
> ./argus_parse.c:2211: warning: passing arg 3 of `sasl_getprop' from
> incompatible pointer type
> ./argus_parse.c:2226: warning: passing arg 4 of `sasl_decode' from
> incompatible pointer type
>
> Now the question is should I go back to cyrus-sasl-1.5.28 which
> seems
> to be the latest 1.x sasl revision or do we want to fix the 2.x code (I
> expect
> I can now munge aclocal.m4 to be happy with the 1.x sasl code too) and leave
> upgrading to the latest sasl version for 2.0.7? I assume the linuxes are
> using
> sasl 1.x code?
>
> Peter Van Epp / Operations and Technical Support
> Simon Fraser University, Burnaby, B.C. Canada
>
>
More information about the argus
mailing list