<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Fail to update vacation msg (using sql driver)</title> 
  <pubDate>Fri, 10 Apr 2026 09:50:16 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6496</link> 
  <atom:link rel="self" type="application/rss+xml" title="Fail to update vacation msg (using sql driver)" href="https://bugs.horde.org/ticket/6496/rss" /> 
  <description>Fail to update vacation msg (using sql driver)</description> 
 
   
   
  <item> 
   <title>Vacation fails to update vacation msg using sql driver and c</title> 
   <description>Vacation fails to update vacation msg using sql driver and crypt as encryption method, thats because the salt used to generate the crypted passwd for the query (WHERE part) does not match the salt in the crypted passwd in the database.



A possible solution should be to remove this lines 

&#039; AND &#039; . $this-&gt;_params[$realm][&#039;pass_col&#039;] . &#039; = ?&#039;;

(lines 89, 107, 147, 189)

from the sql query and just use the user email as the primary search key.



Best regards</description> 
   <pubDate>Tue, 18 Mar 2008 13:47:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t43956</link> 
  </item> 
   
  <item> 
   <title>It looks like that code has been there from the beginning of</title> 
   <description>It looks like that code has been there from the beginning of this driver; I have to say I&#039;m not sure why the password would be used that way (trying to support multiple people with the same email address? I doubt that works...), so removing the password checks seems like a legit option to me.



If it&#039;s not for some reason, we could also make it work by fetching the current password value and passing it in to Auth::getCryptedPassword as the seed.



Anyone know anything about this driver or have an opinion here?</description> 
   <pubDate>Thu, 24 Apr 2008 03:26:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t44853</link> 
  </item> 
   
  <item> 
   <title>&gt; If it&#039;s not for some reason, we could also make it work by</title> 
   <description>&gt; If it&#039;s not for some reason, we could also make it work by fetching 

&gt; the current password value and passing it in to 

&gt; Auth::getCryptedPassword as the seed.



That seems a better solution, my fix was a fast and dirty hack.

Best regards.</description> 
   <pubDate>Thu, 24 Apr 2008 13:14:44 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t44879</link> 
  </item> 
   
  <item> 
   <title>Please test this commit:

http://lists.horde.org/archives/cv</title> 
   <description>Please test this commit:

http://lists.horde.org/archives/cvs/Week-of-Mon-20080421/077738.html</description> 
   <pubDate>Fri, 25 Apr 2008 04:29:48 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t44914</link> 
  </item> 
   
  <item> 
   <title>The patch worked flawlessly, using crypt algorithm.

Thank y</title> 
   <description>The patch worked flawlessly, using crypt algorithm.

Thank you very much.

Best regards...



&gt; Please test this commit:

&gt; http://lists.horde.org/archives/cvs/Week-of-Mon-20080421/077738.html

</description> 
   <pubDate>Fri, 25 Apr 2008 14:46:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t44935</link> 
  </item> 
   
  <item> 
   <title>Excellent, thanks for the feedback.</title> 
   <description>Excellent, thanks for the feedback.</description> 
   <pubDate>Fri, 25 Apr 2008 14:52:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6496#t44937</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
