I managed to run into this issue tonight in a different context, even. 
Should be fixed with this commit:



http://lists.horde.org/archives/cvs/Week-of-Mon-20071203/072846.html

Notice: Undefined offset: 0 in 
/usr/share/php/Horde/Cipher/blowfish.php on line 337

Notice: Undefined offset: 1 in 
/usr/share/php/Horde/Cipher/blowfish.php on line 337

Notice: Undefined offset: 2 in 
/usr/share/php/Horde/Cipher/blowfish.php on line 337

...

Notice: Undefined offset: 71 in 
/usr/share/php/Horde/Cipher/blowfish.php on line 337



The trace of this case is:

ics.php: line 41, $auth->authenticate....

   Auth::authenticate(): line 172, $this->setAuth...

   Auth::setAuth(): line 691, $credentials = Secret::write(Secret::getKey...



       NOTE: here, Secret::getKey() return a empty value because in 
line 146 uses session_id(), and no session has been started



   Secret.php::write():line 52, $cipherCache[$cacheIdx]->setKey($key);

      NOTE: secret.php charge 'blowfish' as default Cipher.php, and 
because $key is empty, blowfish.php gives all the Notice messages.



Hope that information is useful for you



Alfonso

Can you please include (the first few should be enough if there really 
are a lot) the actual error messages?

In some cases, authentication proccess is done without a horde session 
started. That is the case of ics.php.



When you authenticate, throw Auth::setAuth(), there are a 
Secret::getKey('auth') call, and that call uses session_id(). If you 
don have started a horde session, session_id() return a empty value, 
and that causes a lot of Notice php messages in 
Horde/Cipher/blowfish.php (and i don't know if any malfunction)