|
From: SourceForge.net <no...@so...> - 2012-06-18 04:32:54
|
Bugs item #1529379, was opened at 2006-07-26 18:05 Message generated for change (Settings changed) made by pegacat You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=480577&aid=1529379&group_id=55394 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Trudi Ersvaer (trudiersvaer) Assigned to: Nobody/Anonymous (nobody) Summary: jxplorer doesn't report an error when sasl bind fails Initial Comment: When JXplorer connects to the DSA using SASL, if JXplorer doesn't have a correct user certificate, then it just seems to send one anyway. It gets a bind- success, then just does nothing. JX is still usable, but it doesn't show any directory entries until you connect to another DSA successfully ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=480577&aid=1529379&group_id=55394 |