[Adium-devl] libsasl (commits 21692 and 21697)

[Evan Schoenberg]

On Nov 20, 2007, at 3:19 PM, Peter Hosey wrote:

> Fortunately, in investigating for this message, I found that they  
> *are* included on Leopard. But that doesn't help us, since we  
> require Tiger to build.

Ah, this is true.  We build libpurple against the 10.4 SDK, so we only  
get headers included in 10.4 as a result.

Here's what we know so far:
  * With libsasl2.dylib and /usr/lib/sasl2/* that look the same, it  
works for Eric but not for several folks reporting in #8113 on 10.4.  
I've heard no reports of 10.5 failing.  Eric, your sizes and dates  
modified match the listings associated with failure in #8113?
  * When it fails, it's with the PLAIN sasl authentication method.  
PLAIN simply does a Base64 encoding of the username and password, e.g.  
'evanpassword' for a username of evan.  In the failing 10.4 systems,  
the same username and password become 'evanevanpassword' (the username  
is repeated), and the result is Base64 encoded. This, of course, fails  
to authenticate.
  * We end up with the /usr/lib/libsasl2.2.dylib loaded regardless of  
what our libpurple.framework links against because Address  
Book.framework links against LDAP.framework links against /usr/lib/ 
libsasl2.2.dylib.
  * Either way, sasl loads the sasl algorithm plugins from /usr/lib/ 
sasl2.  Note that there's no SDK path in there; the SDKs don't include  
this folder, and the dylibs in the SDKs still use the systemwide folder.

-Evan