<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="/h/themes/default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Security Audit</title> 
  <pubDate>Wed, 22 May 2013 11:46:49 +0000</pubDate> 
  <link>http://bugs.horde.org/ticket/8423</link> 
  <atom:link rel="self" type="application/rss+xml" title="Security Audit" href="http://bugs.horde.org/ticket/8423/rss" /> 
  <description>Security Audit</description> 
 
   
   
  <item> 
   <title>deprecate blatantly insecure auth schemes; make sure to use </title> 
   <description>deprecate blatantly insecure auth schemes; make sure to use a salted auth scheme by default



need a hook or setting to limit # of unsuccessful login attempts to horde



need a hook or setting to limit easily guessable passwords



require re-authentication before changing passwords, or other sensitive operations



don't use the same secret key for multiple purposes

allow key rotation



reference:

http://cookies.lcs.mit.edu/

http://pdos.csail.mit.edu/papers/webauth:sec10.pdf



make sure cookies are set with the secure flag when ssl is used



get rid of URL-based sessions entirely



limit the lifetime of even session-based cookies



authenticator cookie:

exp=t&amp;data=s&amp;digest=MAC(xp=t&amp;data=s)

- push the username and some other basic info (browser string, ip, ... ?) into the data parameter (&quot;s&quot;), to avoid having to init the session on most page loads



- store other session data by key in a backend, accessed on-demand and saved only when dirty? what about commonly used info like prefs? cache with username in the key in the cache backend instead?</description> 
   <pubDate>Fri, 10 Jul 2009 02:57:07 +0000</pubDate> 
   <link>http://bugs.horde.org/ticket/8423#t54887</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
