On Thu, 8 Jul 2004, Quanah Gibson-Mount wrote:
> --On Thursday, July 08, 2004 3:53 PM -0700 Larry Lile
> <[EMAIL PROTECTED]> wrote:
>
> > What would be the "correct" way to handle this? The names have
> > changed in addition the the format of the data. Should Net::LDAP
> > be aware of the SASLv1/v2 difference, should Authen::SASL be hiding
> > the change or should Authen::SASL::Cyrus be more accepting and
> > convert to the appropriate parameter/format?
>
> This is why Authen::SASL::Cyrus gets compiled against the version of SASL
> libraries you want to use, by setting which version to use in Makefile.PL.
> I assume you were doing that, right? :) Authen::SASL::Cyrus can only be
> used with the version of SASL it was compiled against.
Right. But my question goes more to the fact that Net::LDAP.pm calls
$sasl_conn->property(
sockname => $ldap->{net_ldap_socket}->sockname,
peername => $ldap->{net_ldap_socket}->peername,
);
That seems correct for SASLv1, but not for SASLv2. Net::LDAP is
unaware of the SASL version.
So should Net::LDAP be aware of the SASL version and call
something like this when the SASL version is 2?
$sasl_conn->property(
iplocalport => $ldap->{net_ldap_host},
ipremoteport => $ldap->{net_ldap_peer}),
);
--
Larry
