Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.1.0

Bug #18856 Authentication warnings because of wrong Auth_SASL::factory argument
Submitted: 2011-09-21 14:21 UTC
From: dltyfon Assigned: kguest
Status: Closed Package: Auth_SASL
PHP Version: 5.3.8 OS: FreeBSD
Roadmaps: (Not assigned)    

 [2011-09-21 14:21 UTC] dltyfon (Dan Larsson)
Description: ------------ Quick fix is to s/crammd5/CRAM-MD5/ and s/digestmd5/DIGEST-MD5/ on the lines 683 and 707 in Sieve.php. Below is what is installed on the server pear-wise: pear-1.9.3 pear-Auth-1.6.4 pear-Auth_SASL-1.0.5 pear-DB-1.7.13,1 pear-Log-1.12.6 pear-Mail-1.2.0,1 pear-Mail_Mime-1.8.1,2 pear-Net_SMTP-1.6.1 pear-Net_Sieve-1.3.2 pear-Net_Socket-1.0.10 Test script: --------------- Authenticate against a sieve server using the CRAM-MD5 and/or DIGEST-MD5 mechs Expected result: ---------------- No warnings Actual result: -------------- Deprecated mechanism name. Use IANA-registered name: CRAM-MD5. ...and/or... Deprecated mechanism name. Use IANA-registered name: DIGEST-MD5.


 [2011-09-21 14:32 UTC] yunosh (Jan Schneider)
-Status: Open +Status: Assigned -Package: Net_Sieve +Package: Auth_SASL -Assigned To: +Assigned To: kguest
Ken, you cannot deprecate one feature in a release any only add the alternative in the very same release! You shouldn't raise an error at all yet, but only document the deprecated authentication names for now. And please give developers a few releases time to migrate from the deprecated to the new names. I've already seen one hasty release of another package only to fix this.
 [2011-09-22 05:30 UTC] kguest (Ken Guest)
-Status: Assigned +Status: Closed
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Fixed in git for the moment.
 [2011-09-27 20:37 UTC] kguest (Ken Guest)
Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at rolled a new release.