LDAP search broken on IPv6-only
Categories
(Thunderbird :: Address Book, defect)
Tracking
(Not tracked)
People
(Reporter: ondrej, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 Steps to reproduce: 1. Set up an dual-stack LDAP server. 2. Configure address search using this LDAP server. Actual results: On network with native IPv4, search works over IPv4 only all the time. On a single stack IPv6-only network, the search fails. No connection attempt to the IPv6 address of the LDAP server. BTW: It's not possible to configure literal IPv6 address of an LDAP server. Without any error, the config reverts to previously entered value. Enclosing IPv6 literal inside brackets results in invalid address error. Expected results: Address selection should work in the same fashion it works in other parts of Thunderbird.
Comment 1•3 years ago
|
||
Can you create a new profile https://support.mozilla.org/en-US/kb/using-multiple-profiles to see if this reproduces with beta https://archive.mozilla.org/pub/thunderbird/releases/90.0b2/ ?
beta implements new ldap code https://www-stage.thunderbird.net/en-US/thunderbird/90.0beta/releasenotes/
I can confirm that LDAP search works over IPv6 in the 90.0b2. The only remaining problem is that one cannot use IPv6 address literals, only hostnames or IPv4 address literals. Changing the LDAP host name to plain IPv6 address reverts to the previous value without any error, changing to IPv6 address in square brackets results in Invalid Hostname error.
Comment 3•2 years ago
|
||
(In reply to ondrej from comment #2)
I can confirm that LDAP search works over IPv6 in the 90.0b2.
Wfm per reporter, thanks ondrej for reporting back!
The only remaining problem is that one cannot use IPv6 address literals, only hostnames or IPv4 address literals. Changing the LDAP host name to plain IPv6 address reverts to the previous value without any error, changing to IPv6 address in square brackets results in Invalid Hostname error.
I've filed that as Bug 1775292.
Description
•