[python3-ldap] ldap3 0.9.8.4 released

[Giovanni Cannata]

Hello,
ldap3 0.9.8.4 is out, Changelog:

* 0.9.8.4 2015.05.19
    - Added EXTENDED log detail level with prettyPrint description of
ldap messages
    - fixed logging of IPv6 address description
    - fixed checking of open address when dns returns more than one ip
for the same host
    - fixed selection of proper address when failing back from IPv6 to
IPv4 and vice-versa
    - when sending controls controlValue is now optional (as stated in
RFC 4511), specify None to not send it

I refined the logging messages and added an EXTENDED level of details
in logging. At this level each LDAP message (sent or received) is
decoded in the log using the prettyPrint function of the excellent
pyasn1 package. THe line prefix means outgoing (>>) or incoming (<<)
messages For example:

DEBUG:ldap3:EXTENDED:ldap message sent via <ldaps://openldap:636 - ssl
- user: None - unbound - open - <local: 192.168.137.1:50882 - remote:
192.168.137.104:636> - tls not started - listening - SyncStrategy>:
>>LDAPMessage:
>> messageID=2
>> protocolOp=ProtocolOp:
>>  bindRequest=BindRequest:
>>   version=3
>>   name=b''
>>   authentication=AuthenticationChoice:
>>    sasl=SaslCredentials:
>>     mechanism=b'DIGEST-MD5'
>> credentials=b'username="cn=testSASL,o=test",realm="openldap.hyperv",nonce="6o2FZgrC13AywVh7sW6TUatRJxwsothglmQ7TykswbI=",cnonce="a2256f76206ea3b9efc8a6855f508bca",digest-uri="ldap/",qop=auth,nc=00000001,charset="utf-8",response="3681ea074f63ad5c23befec7e5dcd1cf"'
DEBUG:ldap3:NETWORK:sent 283 bytes via <ldaps://openldap:636 - ssl -
user: None - unbound - open - <local: 192.168.137.1:50882 - remote:
192.168.137.104:636> - tls not started - listening - SyncStrategy>
DEBUG:ldap3:NETWORK:received 62 bytes via <ldaps://openldap:636 - ssl
- user: None - unbound - open - <local: 192.168.137.1:50882 - remote:
192.168.137.104:636> - tls not started - listening - SyncStrategy>
DEBUG:ldap3:NETWORK:received 1 ldap messages via <ldaps://openldap:636
- ssl - user: None - unbound - open - <local: 192.168.137.1:50882 -
remote: 192.168.137.104:636> - tls not started - listening -
SyncStrategy>
DEBUG:ldap3:EXTENDED:ldap message received via <ldaps://openldap:636 -
ssl - user: None - unbound - open - <local: 192.168.137.1:50882 -
remote: 192.168.137.104:636> - tls not started - listening -
SyncStrategy>:

<<LDAPMessage:
<< messageID=2
<< protocolOp=ProtocolOp:
<<  bindResponse=BindResponse:
<<   resultCode='invalidCredentials'
<<   matchedDN=b''
<<   diagnosticMessage=b'SASL(-13): user not found: no secret in database'

Bye,
Giovanni