<?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>Horde_Secret: Only store key in cookies if cookies are in use</title> 
  <pubDate>Wed, 08 Apr 2026 17:38:59 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/13284</link> 
  <atom:link rel="self" type="application/rss+xml" title="Horde_Secret: Only store key in cookies if cookies are in use" href="https://bugs.horde.org/ticket/13284/rss" /> 
  <description>Horde_Secret: Only store key in cookies if cookies are in use</description> 
 
   
   
  <item> 
   <title>Hi,

Horde_Secret currently stores the generated key in a </title> 
   <description>Hi,

Horde_Secret currently stores the generated key in a cookie even when cookies are not used for the session id. This happens in setKey() and getKey().

The problem is later on in clearKey(): That one removes the key cookie only if session cookies are in use, too.

The attached patch fixes clearKey() and also avoids setting the cookie at all for non-cookie sessions.

Cheers,
Thomas
</description> 
   <pubDate>Mon, 23 Jun 2014 14:19:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84257</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 6c501804b267</title> 
   <description>Changes have been made in Git (master):

commit 6c501804b267e1559cb16731aaaef9f976ec25fb
Author: Michael M Slusarz &lt;slusarz@horde.org&gt;
Date:   Tue Jun 24 16:06:29 2014 -0600

    [mms] Only store keys in cookie if cookies are in use (Bug #13284; thomas.jarosch@intra2net.com).

 framework/Secret/lib/Horde/Secret.php |   24 +++++++++++++-----------
 framework/Secret/package.xml          |    2 ++
 2 files changed, 15 insertions(+), 11 deletions(-)

http://github.com/horde/horde/commit/6c501804b267e1559cb16731aaaef9f976ec25fb</description> 
   <pubDate>Tue, 24 Jun 2014 22:12:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84267</link> 
  </item> 
   
  <item> 
   <title>Horde_Secret 2.0.3.</title> 
   <description>Horde_Secret 2.0.3.</description> 
   <pubDate>Tue, 24 Jun 2014 22:12:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84269</link> 
  </item> 
   
  <item> 
   <title>&gt; Horde_Secret 2.0.3.

nice, you even eliminated the $set </title> 
   <description>&gt; Horde_Secret 2.0.3.

nice, you even eliminated the $set variable altogether :)
clearKey() looks also much better than my implementation.
</description> 
   <pubDate>Wed, 25 Jun 2014 07:28:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84271</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 512a25022a1f</title> 
   <description>Changes have been made in Git (master):

commit 512a25022a1fa00659372bada8997402a7da01b8
Author: Jan Schneider &lt;jan@horde.org&gt;
Date:   Fri Jul 4 14:14:08 2014 +0200

    Revert &quot;[mms] Only store keys in cookie if cookies are in use (Bug #13284; thomas.jarosch@intra2net.com).&quot;
    
    This reverts commit 6c501804b267e1559cb16731aaaef9f976ec25fb.
    
    This completely broke authentication with any DAV access.
    
    Conflicts:
    	framework/Secret/package.xml

 framework/Secret/lib/Horde/Secret.php |   24 +++++++++++-------------
 1 files changed, 11 insertions(+), 13 deletions(-)

http://github.com/horde/horde/commit/512a25022a1fa00659372bada8997402a7da01b8</description> 
   <pubDate>Fri, 04 Jul 2014 12:15:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84460</link> 
  </item> 
   
  <item> 
   <title>Side note: Cookies are officially not supported for WebDAV s</title> 
   <description>Side note: Cookies are officially not supported for WebDAV sessions (yunosh)

See also:
http://comments.gmane.org/gmane.comp.php.sabredav/65

&quot;2. Don&#039;t use sessions in WebDAV. They are not supported in most clients, and generally a terrible idea. HTTP is supposed to be stateless. Only when your client is a browser, a (session-)cookie is acceptable.&quot;

and

http://stackoverflow.com/questions/14499686/mac-os-x-does-not-send-cookies-to-webdav-resource

We probably need to come up with a more clever storage mechanism.
Funny the previous code worked at all for DAV.

Wild guess: The webdav access generates a new &quot;session id&quot; on every page access since it does not transport the session id cookie. This breaks Horde_Secret because it can no longer decrypt the data of the previous page access.
</description> 
   <pubDate>Fri, 04 Jul 2014 13:30:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13284#t84467</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
